CVE-2026-28420

MEDIUMNVD 4.44.4
EchelonGraph scoreMEDIUM confidence

This medium-severity CVE scores 4.4 under NVD CVSS v3. 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, nvd
4.4EG
EchelonGraph verdictMonitorLow exploitation likelihood right now — keep watching.
  • Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS PROB: 0%CVSS: 4.4Exploit: None knownExposed: 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 version 9.2.0076, a heap-based buffer overflow WRITE and an out-of-bounds READ exist in Vim's terminal emulator when processing maximum combining characters from Unicode supplementary planes. Version 9.2.0076 fixes the issue.

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

Published

February 27, 2026

Last Modified

June 17, 2026

Advisory Details (3)

Auto-updated Aug 6, 2026
🔬 Proof of concept available. Patch available. Sources: github_commit, github.
generic🟡 PoC Available

oss-security - [vim-security] Heap-based Buffer Overflow and OOB Read in :terminal affects Vim < 9.2.0076

http://www.openwall.com/lists/oss-security/2026/02/27/9
github Patch Available

Heap-based Buffer Overflow and OOB Read in :terminal affects Vim < 9.2.0076 · Advisory · vim/vim · GitHub

https://github.com/vim/vim/security/advisories/GHSA-rvj2-jrf9-2phg
github_commit

commit bb6de2105b16 (vim/vim)

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

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

Vendor Advisories for CVE-2026-28420(3)

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

Affected Packages

(5 across 5 ecosystems)
Alpine:v3.23(1)
PackageVulnerable rangeFixed inDependents
vim9.2.0078-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.1.2141-1 (8 versions)2:9.2.0119-1

Weakness Classification(2)

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

All Vendor Advisories

(2)

Every vendor that published an advisory referencing this CVE — pulled from our cve_vendor_advisories aggregation. Click any row for the vendor's original advisory page.

Data Freshness Timeline

(refreshed 7× in last 7d / 28× 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-09-18 19:28 UTCEPSS rescore
  2. 2026-09-18 19:27 UTCEPSS rescore
  3. 2026-09-18 18:50 UTCOSV refresh
  4. 2026-09-17 19:30 UTCEPSS rescore
  5. 2026-09-16 14:08 UTCEPSS rescore
  6. 2026-09-16 05:15 UTCEPSS rescore
  7. 2026-09-13 16:47 UTCEPSS rescore
  8. 2026-09-12 15:01 UTCEPSS rescore
  9. 2026-09-11 14:52 UTCEPSS rescore
  10. 2026-09-10 09:34 UTCEPSS rescore
  11. 2026-09-08 22:00 UTCEPSS rescore
  12. 2026-09-07 16:01 UTCEPSS rescore
  13. 2026-09-06 13:47 UTCEPSS rescore
  14. 2026-09-06 13:47 UTCEPSS rescore
  15. 2026-09-04 05:06 UTCEPSS rescore
  16. 2026-09-02 14:11 UTCEPSS rescore
  17. 2026-09-01 13:53 UTCEPSS rescore
  18. 2026-09-01 04:39 UTCEPSS rescore
  19. 2026-09-01 04:39 UTCEPSS rescore
  20. 2026-08-30 22:04 UTCOSV refresh
  21. 2026-08-30 19:17 UTCEPSS rescore
  22. 2026-08-30 01:22 UTCEPSS rescore
  23. 2026-08-28 21:41 UTCEPSS rescore
  24. 2026-08-27 14:25 UTCEPSS rescore
  25. 2026-08-26 14:46 UTCEPSS rescore
Show 45 more
  1. 2026-08-24 14:17 UTCEPSS rescore
  2. 2026-08-23 00:19 UTCEPSS rescore
  3. 2026-08-21 23:49 UTCEPSS rescore
  4. 2026-08-19 17:03 UTCEPSS rescore
  5. 2026-08-18 13:48 UTCEPSS rescore
  6. 2026-08-17 13:47 UTCEPSS rescore
  7. 2026-08-16 14:56 UTCEPSS rescore
  8. 2026-08-16 02:14 UTCEPSS rescore
  9. 2026-08-15 01:30 UTCEPSS rescore
  10. 2026-08-14 08:48 UTCEG score recompute
  11. 2026-08-14 08:48 UTCVendor advisory
  12. 2026-08-13 22:00 UTCEPSS rescore
  13. 2026-08-13 00:44 UTCEG score recompute
  14. 2026-08-13 00:44 UTCVendor advisory
  15. 2026-08-12 13:50 UTCEPSS rescore
  16. 2026-08-11 13:42 UTCEPSS rescore
  17. 2026-08-11 07:13 UTCEG score recompute
  18. 2026-08-11 07:13 UTCVendor advisory
  19. 2026-08-11 00:00 UTCEPSS rescore
  20. 2026-08-10 08:24 UTCEG score recompute
  21. 2026-08-10 08:24 UTCVendor advisory
  22. 2026-08-09 13:46 UTCEPSS rescore
  23. 2026-08-09 08:26 UTCEG score recompute
  24. 2026-08-09 08:26 UTCVendor advisory
  25. 2026-08-08 16:37 UTCEPSS rescore
  26. 2026-08-07 20:25 UTCEG score recompute
  27. 2026-08-07 20:25 UTCVendor advisory
  28. 2026-08-06 13:46 UTCEPSS rescore
  29. 2026-08-06 02:53 UTCEG score recompute
  30. 2026-08-06 02:53 UTCVendor advisory
  31. 2026-08-05 19:17 UTCEPSS rescore
  32. 2026-08-04 15:10 UTCEPSS rescore
  33. 2026-08-04 04:51 UTCEG score recompute
  34. 2026-08-04 04:51 UTCVendor advisory
  35. 2026-08-03 10:36 UTCEPSS rescore
  36. 2026-08-02 19:18 UTCEG score recompute
  37. 2026-08-02 19:18 UTCVendor advisory
  38. 2026-08-02 02:26 UTCEPSS rescore
  39. 2026-08-01 04:16 UTCEPSS rescore
  40. 2026-07-30 16:27 UTCEPSS rescore
  41. 2026-07-30 01:30 UTCEPSS rescore
  42. 2026-07-28 15:36 UTCEPSS rescore
  43. 2026-07-27 14:02 UTCEG score recompute
  44. 2026-07-27 14:02 UTCVendor advisory
  45. 2026-07-27 13:55 UTCOSV refresh

Frequently asked(5)

What is CVE-2026-28420?
CVE-2026-28420 is a medium vulnerability published on February 27, 2026. Vim is an open source, command line text editor. Prior to version 9.2.0076, a heap-based buffer overflow WRITE and an out-of-bounds READ exist in Vim's terminal emulator when processing maximum combining characters from Unicode supplementary planes. Version 9.2.0076 fixes the issue.
When was CVE-2026-28420 disclosed?
CVE-2026-28420 was first published in the National Vulnerability Database on February 27, 2026, with the most recent update on June 17, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-28420 actively exploited?
CVE-2026-28420 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 92.5% of all scored CVEs.
What is the CVSS score of CVE-2026-28420?
CVE-2026-28420 has a CVSS v3 base score of 4.4 (NVD).
How do I remediate CVE-2026-28420?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-28420, 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-28420

Explore →

Is Your Infrastructure Affected by CVE-2026-28420?

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