CVE-2026-57451

MEDIUMNVD 6.16.1—
EchelonGraph scoreMEDIUM confidence

This medium-severity CVE scores 6.1 under NVD CVSS v3. EPSS exploit probability: 0.1%, top 98% 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).

Triggered by: NVD CVSS baseline
Sources: epss, nvd
Trending — 3 sources updated this week
6.1
EchelonGraph verdictMonitorLow exploitation likelihood right now — keep watching.
  • Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS: 0%CVSS: 6.1Exploit: NoneExposed: 0

No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.

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.

CVSS v3
6.1
EG Score
6.1(medium)
EPSS
1.7%
KEV
Not listed

Published

June 25, 2026

Last Modified

June 26, 2026

Advisory Details (2)

Auto-updated Jun 25, 2026
Patch available. Sources: github_commit, github.
github Patch Available

Out-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-7gpw
github_commit

commit b2338ca90643 (vim/vim)

Fix landed in vim/vim commit b2338ca90643 — awaiting tagged release

https://github.com/vim/vim/commit/b2338ca90643e2f01ecb6547c1172716aaec4f79

Vendor 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.

Weakness Classification(1)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Data Freshness Timeline

(refreshed 24× in last 7d / 35× 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.

  1. 2026-07-06 21:59 UTCEG score recompute
  2. 2026-07-06 21:59 UTCVendor advisory
  3. 2026-07-06 16:27 UTCEPSS rescore
  4. 2026-07-06 16:27 UTCEPSS rescore
  5. 2026-07-06 02:23 UTCEPSS rescore
  6. 2026-07-06 02:23 UTCEPSS rescore
  7. 2026-07-05 23:39 UTCEG score recompute
  8. 2026-07-05 23:39 UTCVendor advisory
  9. 2026-07-05 02:31 UTCEPSS rescore
  10. 2026-07-05 02:30 UTCEPSS rescore
  11. 2026-07-05 01:19 UTCEG score recompute
  12. 2026-07-05 01:19 UTCVendor advisory
  13. 2026-07-04 06:31 UTCEPSS rescore
  14. 2026-07-04 06:31 UTCEPSS rescore
  15. 2026-07-04 02:58 UTCEG score recompute
  16. 2026-07-04 02:58 UTCVendor advisory
  17. 2026-07-03 04:38 UTCEG score recompute
  18. 2026-07-03 04:38 UTCVendor advisory
  19. 2026-07-02 06:16 UTCEG score recompute
  20. 2026-07-02 06:16 UTCVendor advisory
  21. 2026-07-01 07:56 UTCEG score recompute
  22. 2026-07-01 07:56 UTCVendor advisory
  23. 2026-06-30 23:22 UTCEPSS rescore
  24. 2026-06-30 09:35 UTCEG score recompute
  25. 2026-06-29 14:06 UTCEPSS rescore
Show 10 more
  1. 2026-06-29 11:13 UTCEG score recompute
  2. 2026-06-28 14:07 UTCEPSS rescore
  3. 2026-06-28 12:53 UTCEG score recompute
  4. 2026-06-28 04:56 UTCEPSS rescore
  5. 2026-06-27 14:33 UTCEG score recompute
  6. 2026-06-27 03:08 UTCEPSS rescore
  7. 2026-06-26 16:12 UTCEG score recompute▲ 0.80
  8. 2026-06-26 09:42 UTCNVD updateCVSS v3 → 6.1
  9. 2026-06-25 17:52 UTCEG score recompute
  10. 2026-06-25 17:48 UTCNVD updatefirst tracked

Frequently asked(5)

What is CVE-2026-57451?
CVE-2026-57451 is a medium vulnerability published on June 25, 2026. Vim is an open source, command line text editor. Prior to 9.2.0670, gettextprops() 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…
When was CVE-2026-57451 disclosed?
CVE-2026-57451 was first published in the National Vulnerability Database on June 25, 2026, with the most recent update on June 26, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-57451 actively exploited?
CVE-2026-57451 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 1.7% percentile likelihood of exploitation in the next 30 days — higher percentiles indicate greater predicted risk.
What is the CVSS score of CVE-2026-57451?
CVE-2026-57451 has a CVSS v3 base score of 6.1 (NVD).
How do I remediate CVE-2026-57451?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-57451, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

Dependency Blast Radius

Explore the affected products and dependency analysis for CVE-2026-57451

Explore →

Is Your Infrastructure Affected by CVE-2026-57451?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.

Start Free Scan →Browse All CVEs