CVE-2023-48232 [Low] | Security Vulnerability in Vim

Vim is an open source command line text editor. A floating point exception may occur when calculating the line offset for overlong lines and smooth scrolling is enabled and the cpo-settings include the 'n' flag. This may happen when a window border is present and when the wrapped line continues on the next physical line directly in the window border because the 'cpo' setting includes the 'n' flag. Only users with non-default settings are affected and the exception should only result in a crash. This issue has been addressed in commit `cb0b99f0` which has been included in release version 9.0.2107. Users are advised to upgrade. There are no known workarounds for this vulnerability.

#	Date	Old EPSS score	New EPSS score	Delta (New - Old)
1	2025-11-21	0.31%	0.05%	-0.25%
2	2025-11-18	0.05%	0.31%	+0.25%
3	2025-09-22	—	0.05%	—

Date

Old EPSS score

New EPSS score

Delta (New - Old)

2025-11-21

0.31%

0.05%

-0.25%

2025-11-18

0.05%

0.31%

+0.25%

2025-09-22

—

0.05%

—

Base score	Version	Severity	Vector	Exploitability	Impact	Score source
3.9	3.1	LOW	`CVSS:3.1/AV:L/AC:L/PR:L/UI:R/S:U/C:N/I:L/A:L` Click to expand Attack vector (AV:L) They already need access on the box, or another person has to do something wrong; it’s not a remote drive-by. Attack complexity (AC:L) Once they can reach the bug, pulling it off is straightforward—no weird race conditions or rare setup. Privileges required (PR:L) A normal user session is enough; they don’t have to be admin. User interaction (UI:R) A real person has to do something—click, install, enable—otherwise it doesn’t land. Scope (S:U) Damage stays in the same “trust bubble” as the broken component—no big spill into unrelated systems. Confidentiality (C:N) Doesn’t really leak secrets in a meaningful way. Integrity (I:L) Attackers could change some data, but it’s limited—not everything goes. Availability (A:L) Might cause slowdowns, glitches, or partial disruption—not a full brick.	1.3	2.5	[email protected]
4.3	3.1	MEDIUM	`CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:N/A:L` Click to expand Attack vector (AV:N) Could be attacked over the internet or any normal routed network—not just someone sitting at the machine. Attack complexity (AC:L) Once they can reach the bug, pulling it off is straightforward—no weird race conditions or rare setup. Privileges required (PR:N) No account or special rights needed—anonymous or random user is enough. User interaction (UI:R) A real person has to do something—click, install, enable—otherwise it doesn’t land. Scope (S:U) Damage stays in the same “trust bubble” as the broken component—no big spill into unrelated systems. Confidentiality (C:N) Doesn’t really leak secrets in a meaningful way. Integrity (I:N) Data isn’t meaningfully altered or forged. Availability (A:L) Might cause slowdowns, glitches, or partial disruption—not a full brick.	2.8	1.4	[email protected]

Base score

Version

Severity

Vector

Exploitability

Impact

Score source

3.9

3.1

LOW

CVSS:3.1/AV:L/AC:L/PR:L/UI:R/S:U/C:N/I:L/A:L Click to expand

Attack vector (AV:L): They already need access on the box, or another person has to do something wrong; it’s not a remote drive-by.
Attack complexity (AC:L): Once they can reach the bug, pulling it off is straightforward—no weird race conditions or rare setup.
Privileges required (PR:L): A normal user session is enough; they don’t have to be admin.
User interaction (UI:R): A real person has to do something—click, install, enable—otherwise it doesn’t land.
Scope (S:U): Damage stays in the same “trust bubble” as the broken component—no big spill into unrelated systems.
Confidentiality (C:N): Doesn’t really leak secrets in a meaningful way.
Integrity (I:L): Attackers could change some data, but it’s limited—not everything goes.
Availability (A:L): Might cause slowdowns, glitches, or partial disruption—not a full brick.

1.3

2.5

[email protected]

4.3

3.1

MEDIUM

CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:N/A:L Click to expand

Attack vector (AV:N): Could be attacked over the internet or any normal routed network—not just someone sitting at the machine.
Attack complexity (AC:L): Once they can reach the bug, pulling it off is straightforward—no weird race conditions or rare setup.
Privileges required (PR:N): No account or special rights needed—anonymous or random user is enough.
User interaction (UI:R): A real person has to do something—click, install, enable—otherwise it doesn’t land.
Scope (S:U): Damage stays in the same “trust bubble” as the broken component—no big spill into unrelated systems.
Confidentiality (C:N): Doesn’t really leak secrets in a meaningful way.
Integrity (I:N): Data isn’t meaningfully altered or forged.
Availability (A:L): Might cause slowdowns, glitches, or partial disruption—not a full brick.

2.8

1.4

[email protected]

OS Trackers for CVE-2023-48232

vendor	priority	summary	link
`alpine`	—	CVE-2023-48232: 1 source package rows (vim); 182 state rows across 7 repos (3.17-main, 3.18-main, 3.19-main, 3.20-main, 3.21-main, 3.22-main, edge-main); fixed 0, open 182.	https://security.alpinelinux.org/vuln/CVE-2023-48232
`debian`	unimportant	CVE-2023-48232 unimportant priority: Debian including 1 source packages (vim), 5 status rows across 5 suites (bookworm, bullseye, forky, sid, trixie): resolved 3, open 2.	https://security-tracker.debian.org/tracker/CVE-2023-48232
`redhat`	low	—	https://access.redhat.com/security/cve/CVE-2023-48232
`suse`	low	—	https://www.suse.com/security/cve/CVE-2023-48232/
`ubuntu`	medium	CVE-2023-48232 medium priority: Ubuntu including 1 source packages (vim), 8 status rows across 8 suites (bionic, focal, jammy, lunar, mantic, trusty, upstream, xenial): not-affected 5, released 2, needs-triage 1.	https://ubuntu.com/security/CVE-2023-48232

Affected software / configurations for CVE-2023-48232

Vendor	Product	Version	Raw CPE
vim	vim	< 9.0.2107	cpe:2.3:a:vim:vim::::::::
fedoraproject	fedora	37	cpe:2.3:o:fedoraproject:fedora:37:::::::*
fedoraproject	fedora	38	cpe:2.3:o:fedoraproject:fedora:38:::::::*
fedoraproject	fedora	39	cpe:2.3:o:fedoraproject:fedora:39:::::::*

References for CVE-2023-48232

URL	Tags
http://www.openwall.com/lists/oss-security/2023/11/16/1	Mailing List
https://github.com/vim/vim/commit/cb0b99f0672d8446585d26e998343dceca17d1ce	Patch
https://github.com/vim/vim/security/advisories/GHSA-f6cx-x634-hqpw	Vendor Advisory
https://lists.fedoraproject.org/archives/list/[email protected]/message/4UJAK2W5S7G75ETDAEM3BDUCVSXCEGRD/	Mailing List Third Party Advisory
https://lists.fedoraproject.org/archives/list/[email protected]/message/M3VQF7CL3V6FGSEW37WNDFBRRILR65AK/	Mailing List Third Party Advisory
https://lists.fedoraproject.org/archives/list/[email protected]/message/VNRNYLWXZOGTYWE5HMFNQ5FVE3HBUHF6/	Mailing List Third Party Advisory
https://security.netapp.com/advisory/ntap-20231227-0006/	Third Party Advisory

URL

CVE-2023-48232 | Floating point Exception in adjust_plines_for_skipcol() in vim

Exploit prediction scoring system (EPSS) score for CVE-2023-48232

Common vulnerability scoring system (CVSS) metrics for CVE-2023-48232

Weakness enumeration for CVE-2023-48232

OS Trackers for CVE-2023-48232

Affected software / configurations for CVE-2023-48232

References for CVE-2023-48232