CVE-2026-57452

MEDIUMPre-NVD 5.55.5—
EchelonGraph scoreMEDIUM confidence

This medium-severity CVE scores 5.5 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit probability: 0.2%, top 93% 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, secondary
5.5EG
EchelonGraph verdictMonitorLow exploitation likelihood right now — keep watching.
  • Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS PROB: 0%CVSS: 5.5Exploit: None knownExposed: 0

A fix is available — apply it.

Vim is an open source, command line text editor. Prior to 9.2.0671, when Vim opens a file encrypted with the VimCrypt~04! or VimCrypt~05! method (xchacha20poly1305, requires the +sodium feature) whose body is shorter than a single libsodium secretstream header, an unsigned length calculation underflows and a subsequent decryption call reads far past the end of the input buffer, crashing Vim. This vulnerability is fixed in 9.2.0671.

CVSS v3
5.5
EG Score
5.5(medium)
EG Risk
29(Track)
EG Risk 29/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 computed
Severity55% × 45%
Exploitation0% × 40%
Automatability30% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
0%
EPSS %ILE
2%
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 with libsodium-encrypted Files in Vim < 9.2.0671 · Advisory · vim/vim · GitHub

https://github.com/vim/vim/security/advisories/GHSA-c4j9-wr9j-4486
github_commit

commit c8777cec25dc (vim/vim)

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

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

Vendor Advisories for CVE-2026-57452(2)

These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.

Patch Availability(2)

Vendor / EcosystemFixed in / PatchReleasedSource
ubuntuxxd (2:8.2.3995-1ubuntu2.33) @ jammy2026-08-30ubuntu
redhatvim-main-9.2.725-1.hum12026-06-26redhat

Patches are aggregated from vendor advisories (Red Hat, Microsoft, Cisco, GitHub) and package ecosystems (OSV, GHSA). Multiple rows for the same upstream release have been deduplicated.

Affected Packages

(5 across 5 ecosystems)
Alpine:v3.23(1)
PackageVulnerable rangeFixed inDependents
vim—9.2.0854-r0—
Debian:11(1)
PackageVulnerable rangeFixed inDependents
vim2:8.2.2434-3 ... 2:9.2.0858-1 (63 versions)——
Debian:12(1)
PackageVulnerable rangeFixed inDependents
vim2:9.0.1378-2 ... 2:9.2.0858-1 (45 versions)——
Debian:13(1)
PackageVulnerable rangeFixed inDependents
vim2:9.1.1230-2 ... 2:9.2.0858-1 (19 versions)——
Debian:14(1)
PackageVulnerable rangeFixed inDependents
vim2:9.1.1230-2 ... 2:9.2.0524-1 (17 versions)2:9.2.0782-1—

Weakness Classification(2)

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

Additional Vendor Advisories

(1)

Vendors that published advisories for this CVE beyond the curated set above. Broader coverage but minimal per-row detail — click through for the original advisory.

Data Freshness Timeline

(refreshed 5× 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 158 total refreshes for this CVE.

  1. 2026-09-11 14:53 UTCEPSS rescore
  2. 2026-09-10 09:35 UTCEPSS rescore
  3. 2026-09-08 22:01 UTCEPSS rescore
  4. 2026-09-07 16:01 UTCEPSS rescore
  5. 2026-09-06 13:47 UTCEPSS rescore
  6. 2026-09-04 05:07 UTCEPSS rescore
  7. 2026-09-02 14:12 UTCEPSS rescore
  8. 2026-09-01 13:54 UTCEPSS rescore
  9. 2026-08-30 19:34 UTCEG score recompute
  10. 2026-08-30 19:34 UTCVendor advisory
  11. 2026-08-30 19:17 UTCEPSS rescore
  12. 2026-08-28 21:42 UTCEPSS rescore
  13. 2026-08-27 23:22 UTCEG score recompute
  14. 2026-08-27 23:22 UTCVendor advisory
  15. 2026-08-27 14:25 UTCEPSS rescore
  16. 2026-08-26 14:46 UTCEPSS rescore
  17. 2026-08-25 13:49 UTCEPSS rescore
  18. 2026-08-24 13:10 UTCEG score recompute
  19. 2026-08-24 13:10 UTCVendor advisory
  20. 2026-08-23 09:26 UTCEG score recompute
  21. 2026-08-23 09:26 UTCVendor advisory
  22. 2026-08-23 00:19 UTCEPSS rescore
  23. 2026-08-22 10:30 UTCEG score recompute
  24. 2026-08-22 10:30 UTCVendor advisory
  25. 2026-08-21 23:49 UTCEPSS rescore
Show 75 more
  1. 2026-08-21 06:12 UTCEG score recompute
  2. 2026-08-21 06:12 UTCVendor advisory
  3. 2026-08-20 22:55 UTCEPSS rescore
  4. 2026-08-20 07:03 UTCEG score recompute
  5. 2026-08-20 07:03 UTCVendor advisory
  6. 2026-08-19 17:04 UTCEPSS rescore
  7. 2026-08-19 01:24 UTCEG score recompute
  8. 2026-08-19 01:24 UTCVendor advisory
  9. 2026-08-18 13:48 UTCEPSS rescore
  10. 2026-08-17 13:47 UTCEPSS rescore
  11. 2026-08-17 06:37 UTCEG score recompute
  12. 2026-08-17 06:37 UTCVendor advisory
  13. 2026-08-16 14:56 UTCEPSS rescore
  14. 2026-08-16 07:26 UTCEG score recompute
  15. 2026-08-16 07:26 UTCVendor advisory
  16. 2026-08-16 02:14 UTCEPSS rescore
  17. 2026-08-15 08:31 UTCEG score recompute
  18. 2026-08-15 08:31 UTCVendor advisory
  19. 2026-08-15 01:30 UTCEPSS rescore
  20. 2026-08-14 07:37 UTCEG score recompute
  21. 2026-08-14 07:37 UTCVendor advisory
  22. 2026-08-13 22:00 UTCEPSS rescore
  23. 2026-08-13 08:42 UTCEG score recompute
  24. 2026-08-13 08:42 UTCVendor advisory
  25. 2026-08-12 13:51 UTCEPSS rescore
  26. 2026-08-12 09:46 UTCEG score recompute
  27. 2026-08-12 09:46 UTCVendor advisory
  28. 2026-08-11 10:51 UTCEG score recompute
  29. 2026-08-11 10:51 UTCVendor advisory
  30. 2026-08-11 00:00 UTCEPSS rescore
  31. 2026-08-10 11:55 UTCVendor advisory
  32. 2026-08-09 13:00 UTCEG score recompute
  33. 2026-08-09 13:00 UTCVendor advisory
  34. 2026-08-08 16:37 UTCEPSS rescore
  35. 2026-08-08 14:05 UTCEG score recompute
  36. 2026-08-08 14:05 UTCVendor advisory
  37. 2026-08-07 15:09 UTCVendor advisory
  38. 2026-08-06 16:14 UTCEG score recompute
  39. 2026-08-06 16:14 UTCVendor advisory
  40. 2026-08-06 13:47 UTCEPSS rescore
  41. 2026-08-05 19:17 UTCEPSS rescore
  42. 2026-08-05 17:19 UTCVendor advisory
  43. 2026-08-04 18:22 UTCEG score recompute
  44. 2026-08-04 18:22 UTCVendor advisory
  45. 2026-08-04 15:10 UTCEPSS rescore
  46. 2026-08-04 10:39 UTCEPSS rescore
  47. 2026-08-03 19:26 UTCEG score recompute
  48. 2026-08-03 19:26 UTCVendor advisory
  49. 2026-08-03 10:36 UTCEPSS rescore
  50. 2026-08-02 20:31 UTCEG score recompute
  51. 2026-08-02 20:31 UTCVendor advisory
  52. 2026-08-02 02:27 UTCEPSS rescore
  53. 2026-08-01 21:35 UTCEG score recompute
  54. 2026-08-01 21:35 UTCVendor advisory
  55. 2026-08-01 04:16 UTCEPSS rescore
  56. 2026-07-31 22:40 UTCVendor advisory
  57. 2026-07-30 23:44 UTCEG score recompute
  58. 2026-07-30 23:44 UTCVendor advisory
  59. 2026-07-30 16:28 UTCEPSS rescore
  60. 2026-07-30 01:30 UTCEPSS rescore
  61. 2026-07-30 01:30 UTCEPSS rescore
  62. 2026-07-30 00:48 UTCVendor advisory
  63. 2026-07-28 21:10 UTCEG score recompute
  64. 2026-07-28 21:10 UTCVendor advisory
  65. 2026-07-28 15:37 UTCEPSS rescore
  66. 2026-07-27 17:22 UTCEG score recompute
  67. 2026-07-27 17:22 UTCVendor advisory
  68. 2026-07-27 14:14 UTCEPSS rescore
  69. 2026-07-26 14:59 UTCEG score recompute
  70. 2026-07-26 14:59 UTCVendor advisory
  71. 2026-07-26 14:54 UTCEPSS rescore
  72. 2026-07-26 14:54 UTCEPSS rescore
  73. 2026-07-25 14:18 UTCEPSS rescore
  74. 2026-07-25 14:18 UTCEPSS rescore
  75. 2026-07-24 14:18 UTCEPSS rescore

Related CVEs(same vendor + same CWE)

Frequently asked(5)

What is CVE-2026-57452?
CVE-2026-57452 is a medium vulnerability published on June 25, 2026. Vim is an open source, command line text editor. Prior to 9.2.0671, when Vim opens a file encrypted with the VimCrypt~04! or VimCrypt~05! method (xchacha20poly1305, requires the +sodium feature) whose body is shorter than a single libsodium secretstream header, an unsigned length calculation…
When was CVE-2026-57452 disclosed?
CVE-2026-57452 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-57452 actively exploited?
CVE-2026-57452 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0% probability of exploitation in the next 30 days, which ranks it in the top 98.1% of all scored CVEs.
What is the CVSS score of CVE-2026-57452?
CVE-2026-57452 has a CVSS v3 base score of 5.5 (NVD).
How do I remediate CVE-2026-57452?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-57452, 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

See which npm, PyPI, Go, and Maven packages are affected by CVE-2026-57452

Explore →

Is Your Infrastructure Affected by CVE-2026-57452?

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

Start Free Scan →Browse All CVEs