CVE-2026-73071

LOWPre-NVD 3.33.3
EchelonGraph scoreMEDIUM confidence

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

This low-severity CVE scores 3.3 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit probability: 0.1% (1st percentile of EPSS-scored CVEs). No GitHub Security Advisory CVSS is on record for this CVE.

Triggered by: Headline CVSS from a secondary CVSS source
Sources: EPSS, a secondary CVSS source
3.3EG
EchelonGraph verdictMonitorRemediate within your standard update timelines (the SSVC decision on this page).
  • Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS PROB: 0.1%CVSS: 3.3Exploit: None knownExposed services: Not assessed

A fix is available — apply it.

Vim is an open source, command line text editor. From 9.2.0511 until 9.2.0844, json_decode_item() in src/json.c can retain a stale pointer after json_decode_string() invokes channel_fill() to refill and free the current buffer, causing the error path to read freed memory instead of reader->js_buf + reader->js_used when an invalid JSON string spans buffers. This issue is fixed in version 9.2.0844.

CVSS v3
3.3
EG Score
3.3LOWmedium confidence
EG Risk
15
EG Risk 15/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)
Severity33% × 45%
Impact severity (EG Severity): CVSS 3.3 of 10. Never the KEV-floored or EPSS-lifted EG Score.
Exploitation0.1% × 40%
FIRST EPSS: the 30-day exploitation probability when EchelonGraph scored this CVE.
Automatability0% × 15%
CISA's SSVC Automatable value: no (Vulnrichment).
SSVC (CISA's decision table, applied by EchelonGraph): Track at every mission impact level.
Exploitation none (CISA Vulnrichment) · Automatable no (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.
EPSS PROB
0.1%
EPSS %ILE
1st
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 (3.3): severity, escalated by confirmed exploitation. This CVE's 3.3 is its impact severity (EG Severity), not escalated.

EG Severity
3.3 LOWCVSS-B, impact only: no KEV listing, EPSS or EG-KEV tier raises it.a secondary CVSS source · CVSS v3.0 or v3.1
EG Likelihood
0.1% within 30 daysSource: FIRST EPSS (model v2026.06.15, score date 2026-10-17). 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 every mission impact level.CISA BOD 26-04: 60 days if the affected system is publicly exposed; Fix on system upgrade 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 every mission impact level.

A fix is available. Apply it within your standard update timelines.

Exploitation none (CISA Vulnrichment) · Automatable no (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)60 days if the affected system is publicly exposed; Fix on system upgrade if it is not.

In CISA KEV no (CISA's KEV catalog) · Automatable no (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

August 11, 2026

Last Modified

October 6, 2026

References (3)

Vendor Advisories for CVE-2026-73071(1)

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

Patch Availability(1)

Vendor / EcosystemFix (by version range) / PatchReleasedSource
ubuntuxxd (2:8.1.2269-1ubuntu5.32+esm12) @ focal2026-10-06ubuntu

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

(2 across 2 ecosystems)
Alpine:v3.23(1)
PackageVulnerable rangeFix by version rangeDependents
vim—
  • 9.2.0511 up to 9.2.0854-r0: fixed in 9.2.0854-r0
—
Debian:14(1)
PackageVulnerable rangeFix by version rangeDependents
vim2:9.1.1230-2 ... 2:9.2.0782-1 (18 versions)
  • every version up to 2:9.2.0858-1: fixed in 2:9.2.0858-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 8× in last 7d / 37× 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.

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. 3 repeat rows among the latest 93 are merged into the row they repeat.

  1. 2026-10-19 16:33 UTCEPSS rescoreEPSS 0.1% · 1st percentile
  2. 2026-10-18 16:32 UTCEPSS rescoreEPSS 0.1% · 1st percentile
  3. 2026-10-18 03:15 UTCEG score recompute
  4. 2026-10-17 16:35 UTCEPSS rescoreEPSS 0.1% · 1st percentile
  5. 2026-10-16 16:44 UTCEPSS rescoreEPSS 0.1% · 1st percentile
  6. 2026-10-15 16:32 UTCEPSS rescoreEPSS 0.1% · 1st percentile
  7. 2026-10-14 16:33 UTCEPSS rescoreEPSS 0.1% · 1st percentile
  8. 2026-10-13 16:35 UTCEPSS rescoreEPSS 0.2% · 4th percentile
  9. 2026-10-12 15:41 UTCEG score recompute
  10. 2026-10-11 19:26 UTCEG score recompute
  11. 2026-10-11 16:42 UTCEG score recompute
  12. 2026-10-11 14:02 UTCEG score recompute
  13. 2026-10-11 13:49 UTCEPSS rescoreEPSS 0.2% · 4th percentile
  14. 2026-10-10 20:00 UTCEPSS rescoreEPSS 0.2% · 4th percentile
  15. 2026-10-09 20:07 UTCEPSS rescoreEPSS 0.2% · 4th percentile
  16. 2026-10-08 17:13 UTCEPSS rescoreEPSS 0.2% · 4th percentile
  17. 2026-10-07 23:48 UTCEPSS rescoreEPSS 0.2% · 4th percentile
  18. 2026-10-06 20:17 UTCEG score recompute
  19. 2026-10-06 20:17 UTCVendor advisory
  20. 2026-10-06 15:18 UTCEPSS rescoreEPSS 0.2% · 4th percentile
  21. 2026-10-05 17:43 UTCEPSS rescoreEPSS 0.2% · 4th percentile
  22. 2026-10-04 23:22 UTCEPSS rescoreEPSS 0.2% · 4th percentile
  23. 2026-10-04 04:16 UTCEG score recompute
  24. 2026-10-04 04:16 UTCVendor advisory
  25. 2026-10-03 14:26 UTCEPSS rescoreEPSS 0.2% · 4th percentile
Show 65 more
  1. 2026-10-01 19:50 UTCEPSS rescoreEPSS 0.2% · 4th percentile
  2. 2026-09-30 22:18 UTCEG score recompute
  3. 2026-09-30 22:18 UTCVendor advisory
  4. 2026-09-29 15:24 UTCEPSS rescoreEPSS 0.2% · 4th percentile
  5. 2026-09-28 13:52 UTCEPSS rescoreEPSS 0.2% · 4th percentile
  6. 2026-09-27 13:48 UTCEPSS rescoreEPSS 0.2% · 4th percentile
  7. 2026-09-27 10:18 UTCEG score recompute
  8. 2026-09-27 10:18 UTCVendor advisory
  9. 2026-09-26 15:59 UTCEPSS rescoreEPSS 0.2% · 4th percentile
  10. 2026-09-22 16:00 UTCEG score recompute
  11. 2026-09-22 16:00 UTCVendor advisory
  12. 2026-09-21 21:09 UTCEPSS rescoreEPSS 0.1% · 1st percentile
  13. 2026-09-19 12:24 UTCEG score recompute
  14. 2026-09-19 12:24 UTCVendor advisory
  15. 2026-09-18 19:28 UTCEPSS rescoreEPSS 0.1% · 1st percentile
  16. 2026-09-16 14:08 UTCEPSS rescoreEPSS 0.1% · 1st percentile
  17. 2026-09-16 05:15 UTCEPSS rescoreEPSS 0.1% · 1st percentile
  18. 2026-09-16 05:06 UTCEG score recompute
  19. 2026-09-16 05:06 UTCVendor advisory
  20. 2026-09-15 03:12 UTCEPSS rescoreEPSS 0.1% · 1st percentile
  21. 2026-09-13 00:49 UTCEG score recompute
  22. 2026-09-13 00:49 UTCVendor advisory
  23. 2026-09-12 15:02 UTCEPSS rescoreEPSS 0.1% · 1st percentile
  24. 2026-09-11 14:53 UTCEPSS rescoreEPSS 0.1% · 1st percentile
  25. 2026-09-10 09:35 UTCEPSS rescoreEPSS 0.1% · 1st percentile
  26. 2026-09-09 21:02 UTCVendor advisory
  27. 2026-09-09 08:39 UTCEG score recompute
  28. 2026-09-09 08:39 UTCVendor advisory
  29. 2026-09-08 22:01 UTCEPSS rescoreEPSS 0.1% · 1st percentile
  30. 2026-09-06 13:48 UTCEPSS rescoreEPSS 0.1% · 1st percentile
  31. 2026-09-06 05:03 UTCEG score recompute
  32. 2026-09-06 05:03 UTCVendor advisory
  33. 2026-09-04 05:07 UTCEPSS rescoreEPSS 0.1% · 1st percentile
  34. 2026-09-03 01:27 UTCEG score recompute
  35. 2026-09-03 01:27 UTCVendor advisory
  36. 2026-09-01 13:54 UTCEPSS rescoreEPSS 0.1% · 1st percentile
  37. 2026-08-30 19:17 UTCEPSS rescoreEPSS 0.1% · 1st percentile
  38. 2026-08-30 14:58 UTCEG score recompute
  39. 2026-08-30 14:58 UTCVendor advisory
  40. 2026-08-30 01:22 UTCEPSS rescoreEPSS 0.1% · 1st percentile
  41. 2026-08-28 21:42 UTCEPSS rescoreEPSS 0.1% · 1st percentile
  42. 2026-08-27 14:25 UTCEPSS rescoreEPSS 0.1% · 1st percentile
  43. 2026-08-27 11:22 UTCEG score recompute
  44. 2026-08-27 11:22 UTCVendor advisory
  45. 2026-08-26 14:47 UTCEPSS rescoreEPSS 0.1% · 1st percentile
  46. 2026-08-25 13:49 UTCEPSS rescoreEPSS 0.1% · 1st percentile
  47. 2026-08-24 07:46 UTCEG score recompute
  48. 2026-08-24 07:46 UTCVendor advisory
  49. 2026-08-23 00:19 UTCEPSS rescoreEPSS 0.1% · 1st percentile
  50. 2026-08-21 23:49 UTCEPSS rescoreEPSS 0.1% · 1st percentile
  51. 2026-08-21 04:10 UTCEG score recompute
  52. 2026-08-20 22:56 UTCEPSS rescoreEPSS 0.1% · 1st percentile
  53. 2026-08-19 17:04 UTCEPSS rescoreEPSS 0.1% · 1st percentile
  54. 2026-08-18 13:49 UTCEPSS rescoreEPSS 0.1% · 1st percentile
  55. 2026-08-18 00:35 UTCEG score recompute
  56. 2026-08-16 14:56 UTCEPSS rescoreEPSS 0.1% · 1st percentile
  57. 2026-08-16 02:15 UTCEPSS rescoreEPSS 0.1% · 1st percentile
  58. 2026-08-15 01:31 UTCEPSS rescoreEPSS 0.1% · 1st percentile
  59. 2026-08-14 20:56 UTCEG score recompute
  60. 2026-08-13 22:00 UTCEPSS rescoreEPSS 0.1% · 1st percentile
  61. 2026-08-12 13:51 UTCEPSS rescoreEPSS 0.1% · 1st percentile
  62. 2026-08-11 17:20 UTCEG score recompute
  63. 2026-08-11 16:36 UTCEG score recompute
  64. 2026-08-11 15:41 UTCEG score recomputeFirst assessed: 3.3 LOW
  65. 2026-08-11 15:41 UTCMITRE cvelistV5first tracked

Related CVEs(same product + same vendor + same CWE)

Frequently asked(5)

What is CVE-2026-73071?
CVE-2026-73071 is a low-severity vulnerability; its CVE record was published on August 11, 2026. Vim is an open source, command line text editor. From 9.2.0511 until 9.2.0844, jsondecodeitem() in src/json.c can retain a stale pointer after jsondecodestring() invokes channelfill() to refill and free the current buffer, causing the error path to read freed memory instead of reader->jsbuf +…
When was the CVE record for CVE-2026-73071 published?
The CVE record for CVE-2026-73071 was published on August 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 October 6, 2026; the record at its source may have been updated since.
Is CVE-2026-73071 actively exploited?
CVE-2026-73071 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.1% probability of exploitation in the next 30 days (1st percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-73071?
CVE-2026-73071 has a CVSS base score of 3.3 (a secondary CVSS source that NVD displays; NVD's own analysis pending).
How do I remediate CVE-2026-73071?
A fix for CVE-2026-73071 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2026-73071 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-73071

Explore →

Is Your Infrastructure Affected by CVE-2026-73071?

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

Book a Demo →Browse All CVEs