CVE-2026-52859

HIGHNVD 8.28.2
EchelonGraph scoreMEDIUM confidence

“—” beside the score: it is equal to NVD's CVSS score.

This high-severity CVE scores 8.2 under NVD CVSS v3. EPSS exploit probability: 0.3% (23rd percentile of EPSS-scored CVEs). No GitHub Security Advisory CVSS is on record for this CVE.

Triggered by: Headline CVSS from NVD CVSS v3
Sources: EPSS, NVD CVSS v3
Trending — 3 sources updated this week

Also known asEUVD-2026-36283 (ENISA EUVD)Source: ENISA EUVD

8.2EG
EchelonGraph verdictPlan a fixRemediate within your standard update timelines at low or medium mission impact and sooner than that at high (the SSVC decision on this page).
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0.3%CVSS: 8.2Exploit: None knownExposed services: Not assessed

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.2HIGHmedium confidence
EG Risk
52
EG Risk 52/100

EG Risk is EchelonGraph's 0–100 priority score. It fuses impact severity (EG Severity, the CVSS base score, never the KEV-floored or EPSS-lifted EG Score) with real-world exploitation and automatability, under weights EchelonGraph set by hand, so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner.

How it’s computed (value × EchelonGraph’s weight)
Severity82% × 45%
Impact severity (EG Severity): CVSS 8.2 of 10. Never the KEV-floored or EPSS-lifted EG Score.
Exploitation0.3% × 40%
FIRST EPSS: the 30-day exploitation probability when EchelonGraph scored this CVE.
Automatability100% × 15%
CISA's SSVC Automatable value: yes (Vulnrichment).
SSVC (CISA's decision table, applied by EchelonGraph): Track at low or medium mission impact; Attend at high (mission-essential systems).
Exploitation none (CISA Vulnrichment) · Automatable yes (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE.
Action: A fix is available. Apply it within your standard update timelines at low or medium mission impact and sooner than that at high.
EPSS PROB
0.3%
EPSS %ILE
23rd
KEV
Not listed

What the EG score is made of (scorer v4.0: the three questions the 0–10 score mixes, published apart · methodology)

The EG score (8.2): severity, escalated by confirmed exploitation. This CVE's 8.2 is its impact severity (EG Severity), not escalated.

EG Severity
8.2 HIGHCVSS-B, impact only: no KEV listing, EPSS or EG-KEV tier raises it.NVD CVSS v3 · CVSS v3.0 or v3.1
EG Likelihood
0.3% within 30 daysSource: FIRST EPSS (model v2026.06.15, score date 2026-10-30). FIRST's exploitation probability, not an EchelonGraph model.
Confirmed exploitation
None on record (CISA KEV, EG-KEV Tier 1)Reported apart from the likelihood: an observed fact, not a probability.
EG Priority
SSVC Track at medium mission impactTrack at low or medium mission impact; Attend at high (mission-essential systems).CISA BOD 26-04: 14 days if the affected system is publicly exposed; 60 days if it is not.Each input and its source: the SSVC and BOD 26-04 blocks below.

SSVC (CISA's decision table, applied by EchelonGraph)Track at low or medium mission impact; Attend at high (mission-essential systems).

A fix is available. Apply it within your standard update timelines at low or medium mission impact and sooner than that at high.

Exploitation none (CISA Vulnrichment) · Automatable yes (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE. Mission impact is CISA's Mission & Well-being decision point, and only you can judge it. CISA's table makes it high when Mission Prevalence is Essential — the vulnerable component "directly provides capabilities that constitute at least one MEF for at least one entity" (MEF: mission essential function) — or when Public Well-Being Impact is Irreversible: "multiple fatalities are likely", the cyber-physical system "is likely lost or destroyed", "extreme or serious externalities" are imposed on other parties, or social systems such as elections or the financial grid "are destabilized and potentially collapse". CISA's decision table

BOD 26-04 (CISA's remediation timeline, Table 1)14 days if the affected system is publicly exposed; 60 days if it is not.

In CISA KEV no (CISA's KEV catalog) · Automatable yes (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). Whether your system is publicly exposed is yours to answer. BOD 26-04 binds US Federal Civilian Executive Branch agencies; for anyone else it is CISA's published timeline, a reference rather than an obligation. The directive · how EchelonGraph applies it

Published

June 11, 2026

Last Modified

June 15, 2026

Advisory Details (2)

Auto-updated Jun 12, 2026
Patch available. Sources: github_commit, github.
GitHub advisoryMentions a patch (unverified)

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

Patch Availability(7)

Vendor / EcosystemFix (by version range) / PatchReleasedSource
ubuntuvim-tiny (2:7.4.1689-3ubuntu1.5+esm35) @ xenial2026-10-24ubuntu
redhatrhui5/rhua-rhel9:17902420042026-09-24redhat
redhatrhui5/installer-rhel9:17894829612026-09-16redhat
redhatvim-2:8.0.1763-31.el8_10.72026-09-10redhat
redhatvim-2:8.2.2637-26.el9_8.212026-09-10redhat
redhatvim-2:9.1.083-9.el10_2.202026-09-10redhat
redhatvim-main-9.2.967-1.1.hum12026-08-20redhat

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 rangeFix by version rangeDependents
vim—
  • every version up to 9.2.0567-r0: fixed in 9.2.0567-r0
—
Debian:11(1)
PackageVulnerable rangeFix by version rangeDependents
vim2:8.2.2434-3 ... 2:9.2.0858-1 (63 versions)
  • every version on: no fix on record
—
Debian:12(1)
PackageVulnerable rangeFix by version rangeDependents
vim2:9.0.1378-2 ... 2:9.2.0858-1 (45 versions)
  • every version on: no fix on record
—
Debian:13(1)
PackageVulnerable rangeFix by version rangeDependents
vim2:9.1.1230-2 ... 2:9.2.0858-1 (19 versions)
  • every version on: no fix on record
—
Debian:14(1)
PackageVulnerable rangeFix by version rangeDependents
vim2:9.1.1230-2 ... 2:9.2.0524-1 (17 versions)
  • every version up to 2:9.2.0782-1: fixed in 2:9.2.0782-1
—

Weakness Classification(1)

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 10× in last 7d / 42× in last 30d)

Each row is a time one of our pipelines fetched, updated or re-scored this CVE. 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. An arrow marks a change the record states ("CVSS v3 → 9.1"); EPSS and GHSA rows show the values recorded at that time, not what changed (EPSS values are rounded; hover one for the exact figures). Most recent first.

Showing the most recent 100 of 290 refreshes on record for this CVE.

A repeat, a row identical to one the same pipeline wrote less than 10 seconds earlier, is not a separate refresh and is not counted. None are among the latest 100 rows. The 190 oldest rows on record are not shown and were not checked, so the counts can still include repeats.

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

Frequently asked(5)

What is CVE-2026-52859?
CVE-2026-52859 is a high-severity vulnerability; its CVE record was 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 the CVE record for CVE-2026-52859 published?
The CVE record for CVE-2026-52859 was published on June 11, 2026. That is the record's publication date; the vulnerability itself may have been made public earlier. EchelonGraph's copy of the record carries a last-modified date of June 15, 2026; the record at its source may have been updated since.
Is CVE-2026-52859 actively exploited?
CVE-2026-52859 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.3% probability of exploitation in the next 30 days (23rd percentile of EPSS-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?
A fix for CVE-2026-52859 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2026-52859 are linked in the Vendor Advisories panel on this page.

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.