CVE-2026-73074

HIGHPre-NVD 7.17.1—
EchelonGraph scoreMEDIUM confidence

This high-severity CVE scores 7.1 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit probability: 0.1%, top 99% 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
7.1EG
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0%CVSS: 7.1Exploit: None knownExposed: 0

A fix is available — apply it.

Vim is an open source, command line text editor. Prior to 9.2.0841, prop_add_one() in src/textprop.c uses the proplen value from get_text_props() to increment a uint16_t property count beyond 0xffff, wrapping the count to zero and copying existing text-property records into a heap allocation sized for none of them. This issue is fixed in version 9.2.0841.

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

Published

August 11, 2026

Last Modified

September 9, 2026

Advisory Details (2)

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

commit a9336b476fd1 (vim/vim)

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

https://github.com/vim/vim/commit/a9336b476fd1a182e3f79b5f83c0ffb04f8a922b
github Patch Available

Heap Buffer Overflow in Text Property Handling in Vim < 9.2.0841 · Advisory · vim/vim · GitHub

https://github.com/vim/vim/security/advisories/GHSA-hm4g-pjfx-m27j

Patch Availability(1)

Vendor / EcosystemFixed in / PatchReleasedSource
ubuntuxxd (2:8.2.3995-1ubuntu2.35) @ jammy2026-09-21ubuntu

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

(4 across 4 ecosystems)
Alpine:v3.23(1)
PackageVulnerable rangeFixed inDependents
vim—9.2.0854-r0—
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.0782-1 (18 versions)2:9.2.0858-1—

Weakness Classification(1)

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 23× in last 7d / 103× 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 129 total refreshes for this CVE.

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

Related CVEs(same vendor + same CWE)

Frequently asked(5)

What is CVE-2026-73074?
CVE-2026-73074 is a high vulnerability published on August 11, 2026. Vim is an open source, command line text editor. Prior to 9.2.0841, propaddone() in src/textprop.c uses the proplen value from gettextprops() to increment a uint16_t property count beyond 0xffff, wrapping the count to zero and copying existing text-property records into a heap allocation sized for…
When was CVE-2026-73074 disclosed?
CVE-2026-73074 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-73074 actively exploited?
CVE-2026-73074 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.7% of all scored CVEs.
What is the CVSS score of CVE-2026-73074?
CVE-2026-73074 has a CVSS v3 base score of 7.1 (NVD).
How do I remediate CVE-2026-73074?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-73074, 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-73074

Explore →

Is Your Infrastructure Affected by CVE-2026-73074?

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

Start Free Scan →Browse All CVEs