CVE-2026-57451 [Medium] | Out-of-bounds Read in Vim

Vim is an open source, command line text editor. Prior to 9.2.0670, get_text_props() in src/textprop.c reads a uint16 property count stored inline after a line's text and returns it as the number of 32-byte textprop_T entries that follow. The only check is a floor that guarantees room for a single entry; the count is never checked against the amount of data actually present. A line that declares a large count while carrying little data causes consumers to read far past the end of the line buffer. Such a line can be delivered through a crafted undo file, leading to a crash. This vulnerability is fixed in 9.2.0670.

#	Date	Old EPSS score	New EPSS score	Delta (New - Old)
1	2026-06-26	—	0.11%	—

Date

Old EPSS score

New EPSS score

Delta (New - Old)

2026-06-26

—

0.11%

—

Base score	Version	Severity	Vector	Exploitability	Impact	Score source
5.3	3.1	MEDIUM	`CVSS:3.1/AV:L/AC:H/PR:N/UI:R/S:U/C:L/I:N/A:H` 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:H) Even with access, the exploit needs extra luck, timing, or a fussy environment to actually work. 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:L) Some sensitive info could get out, but not a total data dump. Integrity (I:N) Data isn’t meaningfully altered or forged. Availability (A:H) Could take the service down hard or make it unusable for people who depend on it.	1.0	4.2	[email protected]
6.1	3.1	MEDIUM	`CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:L/I:N/A:H` 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: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:L) Some sensitive info could get out, but not a total data dump. Integrity (I:N) Data isn’t meaningfully altered or forged. Availability (A:H) Could take the service down hard or make it unusable for people who depend on it.	1.8	4.2	[email protected]

Base score

Version

Severity

Vector

Exploitability

Impact

Score source

5.3

3.1

MEDIUM

CVSS:3.1/AV:L/AC:H/PR:N/UI:R/S:U/C:L/I:N/A:H 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:H): Even with access, the exploit needs extra luck, timing, or a fussy environment to actually work.
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:L): Some sensitive info could get out, but not a total data dump.
Integrity (I:N): Data isn’t meaningfully altered or forged.
Availability (A:H): Could take the service down hard or make it unusable for people who depend on it.

1.0

4.2

[email protected]

6.1

3.1

MEDIUM

CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:L/I:N/A:H 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: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:L): Some sensitive info could get out, but not a total data dump.
Integrity (I:N): Data isn’t meaningfully altered or forged.
Availability (A:H): Could take the service down hard or make it unusable for people who depend on it.

1.8

4.2

[email protected]

OS Trackers for CVE-2026-57451

vendor	priority	summary	link
`debian`	not yet assigned	CVE-2026-57451 not yet assigned priority: Debian including 1 source packages (vim), 5 status rows across 5 suites (bookworm, bullseye, forky, sid, trixie): open 5.	https://security-tracker.debian.org/tracker/CVE-2026-57451
`suse`	medium	—	https://www.suse.com/security/cve/CVE-2026-57451/
`ubuntu`	medium	CVE-2026-57451 medium priority: Ubuntu including 1 source packages (vim), 9 status rows across 9 suites (bionic, focal, jammy, noble, questing, resolute, trusty, upstream, xenial): not-affected 9.	https://ubuntu.com/security/CVE-2026-57451

Affected software / configurations for CVE-2026-57451

Vendor	Product	Version	Raw CPE
vim	vim	< 9.2.0670	cpe:2.3:a:vim:vim::::::::

References for CVE-2026-57451

URL	Tags
https://github.com/vim/vim/commit/b2338ca90643e2f01ecb6547c1172716aaec4f79	Patch
https://github.com/vim/vim/releases/tag/v9.2.0670	Product
https://github.com/vim/vim/security/advisories/GHSA-f36c-2qcp-7gpw	Vendor Advisory

URL

CVE-2026-57451 | Vim: Out-of-bounds Read in Text Property Count

Exploit prediction scoring system (EPSS) score for CVE-2026-57451

Common vulnerability scoring system (CVSS) metrics for CVE-2026-57451

Weakness enumeration for CVE-2026-57451

OS Trackers for CVE-2026-57451

Affected software / configurations for CVE-2026-57451

References for CVE-2026-57451