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.
CVE-2026-57451
This medium-severity CVE scores 6.1 under NVD CVSS v3. EPSS exploit probability: 0.2%, top 94% of all CVEs by exploit prediction. GitHub Security Advisory data not yet ingested — confidence will rise once GHSA publishes (typical lag: hours to days for open-source ecosystem CVEs; never for infrastructure-only CVEs).
- Lower severity and no public exploit yet
No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.
- CVSS v3
- 6.1
- EG Score
- 6.1(medium)
- EG Risk
- 32(Track)EG Risk 32/100SSVC: Track
EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).
How it’s computedSeverity61% × 45%Exploitation0% × 40%Automatability30% × 15%Action: Routine — remediate on your standard cadence. - EPSS PROB
- 0%
- EPSS %ILE
- 6%
- KEV
- Not listed
Published
June 25, 2026
Last Modified
June 26, 2026
Advisory Details (2)
Auto-updated Jun 25, 2026Out-of-bounds Read in Text Property Count in Vim < 9.2.0670 · Advisory · vim/vim · GitHub
https://github.com/vim/vim/security/advisories/GHSA-f36c-2qcp-7gpwcommit b2338ca90643 (vim/vim)
Fix landed in vim/vim commit b2338ca90643 — awaiting tagged release
https://github.com/vim/vim/commit/b2338ca90643e2f01ecb6547c1172716aaec4f79Vendor Advisories for CVE-2026-57451(1)
These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.
Affected Packages
(2 across 2 ecosystems)
Alpine:v3.23(1)
| Package | Vulnerable range | Fixed in | Dependents |
|---|---|---|---|
| vim | — | 9.2.0854-r0 | — |
Debian:14(1)
| Package | Vulnerable range | Fixed in | Dependents |
|---|---|---|---|
| vim | 2:9.1.1230-2 ... 2:9.2.0524-1 (17 versions) | 2:9.2.0782-1 | — |
Weakness Classification(1)
MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.
Data Freshness Timeline
(refreshed 4× in last 7d / 49× in last 30d)
Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.
Showing the most recent 100 of 150 total refreshes for this CVE.
- 2026-09-10 09:35 UTCEPSS rescore
- 2026-09-08 22:01 UTCEPSS rescore
- 2026-09-07 16:01 UTCEPSS rescore
- 2026-09-06 13:47 UTCEPSS rescore
- 2026-09-04 05:07 UTCEPSS rescore
- 2026-09-02 14:12 UTCEPSS rescore
- 2026-09-01 13:54 UTCEPSS rescore
- 2026-09-01 04:40 UTCEPSS rescore
- 2026-08-30 19:34 UTCEG score recompute
- 2026-08-30 19:34 UTCVendor advisory
- 2026-08-30 19:17 UTCEPSS rescore
- 2026-08-30 01:22 UTCEPSS rescore
- 2026-08-28 21:42 UTCEPSS rescore
- 2026-08-27 23:22 UTCEG score recompute
- 2026-08-27 23:22 UTCVendor advisory
- 2026-08-27 14:25 UTCEPSS rescore
- 2026-08-26 14:46 UTCEPSS rescore
- 2026-08-25 13:49 UTCEPSS rescore
- 2026-08-24 13:10 UTCEG score recompute
- 2026-08-24 13:10 UTCVendor advisory
- 2026-08-23 08:56 UTCEG score recompute
- 2026-08-23 08:56 UTCVendor advisory
- 2026-08-23 00:19 UTCEPSS rescore
- 2026-08-22 10:31 UTCEG score recompute
- 2026-08-22 10:31 UTCVendor advisory
Show 75 moreShow fewer
- 2026-08-21 23:49 UTCEPSS rescore
- 2026-08-21 05:24 UTCEG score recompute
- 2026-08-21 05:24 UTCVendor advisory
- 2026-08-20 22:55 UTCEPSS rescore
- 2026-08-20 07:03 UTCEG score recompute
- 2026-08-20 07:03 UTCVendor advisory
- 2026-08-19 17:04 UTCEPSS rescore
- 2026-08-19 01:24 UTCEG score recompute
- 2026-08-19 01:24 UTCVendor advisory
- 2026-08-18 13:48 UTCEPSS rescore
- 2026-08-17 13:47 UTCEPSS rescore
- 2026-08-17 11:56 UTCEG score recompute
- 2026-08-17 11:56 UTCVendor advisory
- 2026-08-16 14:56 UTCEPSS rescore
- 2026-08-16 13:36 UTCEG score recompute
- 2026-08-16 13:36 UTCVendor advisory
- 2026-08-16 02:14 UTCEPSS rescore
- 2026-08-15 15:16 UTCEG score recompute
- 2026-08-15 15:16 UTCVendor advisory
- 2026-08-15 01:30 UTCEPSS rescore
- 2026-08-14 16:56 UTCEG score recompute
- 2026-08-14 16:56 UTCVendor advisory
- 2026-08-13 22:00 UTCEPSS rescore
- 2026-08-13 18:29 UTCVendor advisory
- 2026-08-12 19:07 UTCEG score recompute
- 2026-08-12 19:07 UTCVendor advisory
- 2026-08-12 13:51 UTCEPSS rescore
- 2026-08-11 20:47 UTCEG score recompute
- 2026-08-11 20:47 UTCVendor advisory
- 2026-08-11 00:00 UTCEPSS rescore
- 2026-08-10 00:06 UTCEG score recompute
- 2026-08-09 13:46 UTCEPSS rescore
- 2026-08-09 01:46 UTCEG score recompute
- 2026-08-09 01:46 UTCVendor advisory
- 2026-08-08 16:37 UTCEPSS rescore
- 2026-08-07 05:06 UTCEG score recompute
- 2026-08-07 05:06 UTCVendor advisory
- 2026-08-06 13:47 UTCEPSS rescore
- 2026-08-06 06:46 UTCEG score recompute
- 2026-08-06 06:46 UTCVendor advisory
- 2026-08-05 19:17 UTCEPSS rescore
- 2026-08-05 08:26 UTCEG score recompute
- 2026-08-05 08:26 UTCVendor advisory
- 2026-08-04 15:10 UTCEPSS rescore
- 2026-08-04 10:39 UTCEPSS rescore
- 2026-08-04 08:57 UTCEG score recompute
- 2026-08-04 08:57 UTCVendor advisory
- 2026-08-03 10:36 UTCEPSS rescore
- 2026-08-02 09:05 UTCEG score recompute
- 2026-08-02 09:05 UTCVendor advisory
- 2026-08-02 02:27 UTCEPSS rescore
- 2026-08-01 10:45 UTCEG score recompute
- 2026-08-01 10:45 UTCVendor advisory
- 2026-08-01 04:16 UTCEPSS rescore
- 2026-07-31 12:25 UTCVendor advisory
- 2026-07-30 14:03 UTCEG score recompute
- 2026-07-30 14:03 UTCVendor advisory
- 2026-07-30 01:30 UTCEPSS rescore
- 2026-07-30 01:30 UTCEPSS rescore
- 2026-07-29 13:34 UTCEG score recompute
- 2026-07-29 13:34 UTCVendor advisory
- 2026-07-28 15:37 UTCEPSS rescore
- 2026-07-28 15:13 UTCEG score recompute
- 2026-07-28 15:13 UTCVendor advisory
- 2026-07-27 14:14 UTCEPSS rescore
- 2026-07-27 13:19 UTCVendor advisory
- 2026-07-26 14:59 UTCEG score recompute
- 2026-07-26 14:59 UTCVendor advisory
- 2026-07-25 14:18 UTCEPSS rescore
- 2026-07-25 14:18 UTCEPSS rescore
- 2026-07-24 14:18 UTCEPSS rescore
- 2026-07-24 14:18 UTCEPSS rescore
- 2026-07-23 03:20 UTCEG score recompute
- 2026-07-22 14:08 UTCEPSS rescore
- 2026-07-22 14:08 UTCEPSS rescore
Related CVEs(same vendor + same CWE)
Same vendor
10 shownmsrc
Same CWE
10 shownCWE-125
- CVE-2013-0767EG 10.0EPSS p93HIGH
- CVE-2009-2523EG 10.0EPSS p98HIGH
- CVE-2014-2898EG 9.8CRITICAL
- CVE-2014-2897EG 9.8CRITICAL
- CVE-2014-2896EG 9.8CRITICAL
- CVE-1999-0006EG 9.8EPSS p96CRITICAL
- CVE-2014-1522EG 9.3EPSS p92HIGH
- CVE-2013-0779EG 9.3EPSS p92HIGH
- CVE-2013-0778EG 9.3EPSS p90HIGH
- CVE-2012-3995EG 9.3EPSS p92HIGH
Frequently asked(5)
What is CVE-2026-57451?
When was CVE-2026-57451 disclosed?
Is CVE-2026-57451 actively exploited?
What is the CVSS score of CVE-2026-57451?
How do I remediate CVE-2026-57451?
Dependency Blast Radius
See which npm, PyPI, Go, and Maven packages are affected by CVE-2026-57451
Is Your Infrastructure Affected by CVE-2026-57451?
EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.