CVE-2026-73075

MEDIUMPre-NVD 4.64.6
EchelonGraph scoreMEDIUM confidence

This medium-severity CVE scores 4.6 under a secondary CVSS source (NVD's own analysis pending). 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, secondary
Trending — 3 sources updated this week
4.6EG
EchelonGraph verdictMonitorLow exploitation likelihood right now — keep watching.
  • Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS PROB: 0%CVSS: 4.6Exploit: 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. From 9.2.0469 until 9.2.0843, popup_mark_opacity_zindex() in src/popupwin.c can use a negative w_winrow for a text-property-anchored popup with clipwindow and opacity, indexing before the screen array instead of accounting for w_popup_topoff and causing an out-of-bounds read and conditional write. This issue is fixed in version 9.2.0843.

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

Published

August 11, 2026

Last Modified

September 9, 2026

Advisory Details (1)

Auto-updated Aug 11, 2026
Patch available. Sources: github.
github Patch Available

Out-of-bounds Access in Popup Opacity Handling in Vim >= 9.2.0469 && Vim < 9.2.0843 · Advisory · vim/vim · GitHub

https://github.com/vim/vim/security/advisories/GHSA-pmvp-6rcj-98p4

Affected Packages

(2 across 2 ecosystems)
Alpine:v3.23(1)
PackageVulnerable rangeFixed inDependents
vim9.2.0854-r0
Debian:14(1)
PackageVulnerable rangeFixed inDependents
vim2:9.1.1230-2 ... 2:9.2.0782-1 (18 versions)2:9.2.0858-1

Weakness Classification(2)

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

All Vendor Advisories

(1)

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

Frequently asked(5)

What is CVE-2026-73075?
CVE-2026-73075 is a medium vulnerability published on August 11, 2026. Vim is an open source, command line text editor. From 9.2.0469 until 9.2.0843, popupmarkopacityzindex() in src/popupwin.c can use a negative wwinrow for a text-property-anchored popup with clipwindow and opacity, indexing before the screen array instead of accounting for wpopuptopoff and causing an…
When was CVE-2026-73075 disclosed?
CVE-2026-73075 was first published in the National Vulnerability Database on August 11, 2026, with the most recent update on September 9, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-73075 actively exploited?
CVE-2026-73075 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-73075?
CVE-2026-73075 has a CVSS v3 base score of 4.6 (NVD).
How do I remediate CVE-2026-73075?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-73075, 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-73075

Explore →

Is Your Infrastructure Affected by CVE-2026-73075?

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