CVE-2026-52859

HIGHNVD 8.28.2—
EchelonGraph scoreMEDIUM confidence

This high-severity CVE scores 8.2 under NVD CVSS v3. EPSS exploit probability: 0.3%, top 77% 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 — Patch released this week
8.2EG
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0%CVSS: 8.2Exploit: None knownExposed: 0

A fix is available — apply it.

Vim is an open source, command line text editor. Prior to version 9.2.0565, the update_snapshot() function in src/terminal.c copies the visible terminal screen into the scrollback buffer when a snapshot is taken. For each screen cell it walks the cell's chars[] array with no upper bound, stopping only when it encounters a NUL terminator. When a cell legitimately fills all VTERM_MAX_CHARS_PER_CELL (6) slots — a base character plus five combining marks — the bundled libvterm returns the array without a terminating NUL, so the loop reads past the fixed six-element array and appends the out-of-bounds values to a buffer reserved for only six characters. A program whose output is rendered inside a :terminal window can trigger this with a short byte sequence and no Vim scripting, leading to a crash. This issue has been patched in version 9.2.0565.

CVSS v3
8.2
EG Score
8.2(medium)
EG Risk
42(Track)
EG Risk 42/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
Severity82% × 45%
Exploitation0% × 40%
Automatability30% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
0%
EPSS %ILE
23%
KEV
Not listed

Published

June 11, 2026

Last Modified

June 15, 2026

Advisory Details (2)

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

Out-of-bounds Read in Terminal Screen Snapshot in Vim < 9.2.0565 · Advisory · vim/vim · GitHub

https://github.com/vim/vim/security/advisories/GHSA-47gw-8gc3-mgcm
github_commit

commit 63680c6d3d52 (vim/vim)

Fix landed in vim/vim commit 63680c6d3d52 — awaiting tagged release

https://github.com/vim/vim/commit/63680c6d3d52477817b49cd1a66e7aabe8a7aa19

Vendor Advisories for CVE-2026-52859(1)

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

Patch Availability(4)

Vendor / EcosystemFixed in / PatchReleasedSource
ubuntuxxd (2:9.1.2141-1ubuntu4.5) @ resolute2026-09-14ubuntu
redhatvim-2:9.1.083-9.el10_2.202026-09-10redhat
redhatvim-2:8.0.1763-31.el8_10.72026-09-10redhat
redhatvim-2:8.2.2637-26.el9_8.212026-09-10redhat

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.0567-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(1)

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

Additional Vendor Advisories

(4)

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 6× in last 7d / 41× 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 238 total refreshes for this CVE.

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

Frequently asked(5)

What is CVE-2026-52859?
CVE-2026-52859 is a high vulnerability published on June 11, 2026. Vim is an open source, command line text editor. Prior to version 9.2.0565, the updatesnapshot() function in src/terminal.c copies the visible terminal screen into the scrollback buffer when a snapshot is taken. For each screen cell it walks the cell's chars[] array with no upper bound, stopping…
When was CVE-2026-52859 disclosed?
CVE-2026-52859 was first published in the National Vulnerability Database on June 11, 2026, with the most recent update on June 15, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-52859 actively exploited?
CVE-2026-52859 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 77.1% of all scored CVEs.
What is the CVSS score of CVE-2026-52859?
CVE-2026-52859 has a CVSS v3 base score of 8.2 (NVD).
How do I remediate CVE-2026-52859?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-52859, 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-52859

Explore →

Is Your Infrastructure Affected by CVE-2026-52859?

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

Start Free Scan →Browse All CVEs