CVE-2026-73064

LOWPre-NVD 2.92.9—
EchelonGraph scoreHIGH confidence

Score 2.9 from GitHub Security Advisory (severity: LOW) published 2026-09-24. A secondary CVSS source baseline 2.9; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa, secondary
Trending — 4 sources updated this week
2.9EG
EchelonGraph verdictMonitorLow exploitation likelihood right now — keep watching.
  • Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS PROB: 0.1%CVSS: 2.9Exploit: None knownExposed services: Not assessed

No fix is confirmed yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for the fix.

In Mbed TLS 3.2.0 though 3.6.6 and 4.0.0 through 4.1.0, an attacker who can cause an entropy source to fail can remove or inject bytes into the start of the TLS stream. This only affects TLS 1.3 servers.

CVSS v3
2.9
EG Score
2.9LOWhigh confidence
EG Risk
13
EG Risk 13/100CISA SSVC

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
Severity29% × 45%
Exploitation0% × 40%
Automatability0% × 15%
CISA SSVC: Track at every mission impact level.
Action: No fix is confirmed yet. Restrict network exposure of the affected system or apply the vendor's mitigation within your standard update timelines, and watch the vendor's advisory for the fix.
EPSS PROB
0.1%
EPSS %ILE
below the 1st
KEV
Not listed

CISA SSVCTrack at every mission impact level.

No fix is confirmed yet. Restrict network exposure of the affected system or apply the vendor's mitigation within your standard update timelines, and watch the vendor's advisory for the fix.

Exploitation none (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). Mission impact is CISA's Mission & Well-being decision point, and only you can judge it: high means the affected system is essential to your organisation's mission, or its compromise could cause irreversible harm to people. CISA's decision table

Published

September 24, 2026

Last Modified

September 24, 2026

References (2)

Vendor Advisories for CVE-2026-73064(2)

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

Affected Packages

(3 across 3 ecosystems)
Debian:12(1)
PackageVulnerable rangeFix by version rangeDependents
mbedtls2.28.3-1 ... 3.6.7-3 (23 versions)
  • every version on: no fix on record
—
Debian:13(1)
PackageVulnerable rangeFix by version rangeDependents
mbedtls3.6.4-2 ... 3.6.7-3 (7 versions)
  • every version on: no fix on record
—
Debian:14(1)
PackageVulnerable rangeFix by version rangeDependents
mbedtls3.6.4-2, 3.6.5-0.1, 3.6.5-0.1~deb13u1, 3.6.6-0.1, 3.6.6-0.1~deb13u1
  • every version up to 3.6.7-1: fixed in 3.6.7-1
—

Weakness Classification(1)

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

Data Freshness Timeline

(refreshed 7× in last 7d / 19× 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-10-03 23:30 UTCEG score recompute
  2. 2026-10-03 23:30 UTCVendor advisory
  3. 2026-10-03 23:30 UTCGHSA enrichment
  4. 2026-10-01 19:50 UTCEPSS rescore
  5. 2026-09-30 22:45 UTCEG score recompute
  6. 2026-09-30 22:45 UTCGHSA enrichment
  7. 2026-09-29 15:24 UTCEPSS rescore
  8. 2026-09-27 22:00 UTCEG score recompute
  9. 2026-09-27 22:00 UTCGHSA enrichment
  10. 2026-09-27 13:48 UTCEPSS rescore
  11. 2026-09-26 15:59 UTCEPSS rescore
  12. 2026-09-24 21:15 UTCGHSA enrichment
  13. 2026-09-24 18:36 UTCEG score recompute
  14. 2026-09-24 18:36 UTCGHSA enrichment
  15. 2026-09-24 18:02 UTCEG score recompute
  16. 2026-09-24 18:02 UTCGHSA enrichment
  17. 2026-09-24 15:28 UTCEG score recompute
  18. 2026-09-24 15:02 UTCEG score recompute
  19. 2026-09-24 15:01 UTCMITRE cvelistV5first tracked

Related CVEs(same CWE)

Frequently asked(5)

What is CVE-2026-73064?
CVE-2026-73064 is a low vulnerability published on September 24, 2026. In Mbed TLS 3.2.0 though 3.6.6 and 4.0.0 through 4.1.0, an attacker who can cause an entropy source to fail can remove or inject bytes into the start of the TLS stream. This only affects TLS 1.3 servers.
When was CVE-2026-73064 disclosed?
CVE-2026-73064 was first published on September 24, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-73064 actively exploited?
CVE-2026-73064 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.1% probability of exploitation in the next 30 days (below the 1st percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-73064?
CVE-2026-73064 has a CVSS base score of 2.9 (a secondary CVSS source that NVD displays; NVD's own analysis pending).
How do I remediate CVE-2026-73064?
No fix for CVE-2026-73064 is confirmed yet. Until one is published, restrict network exposure of the affected system or apply the vendor's mitigation — for example, keep it off the internet or limit it to trusted networks — and watch the vendor's advisory for the fix. The vendor advisories EchelonGraph has for CVE-2026-73064 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-73064

Explore →

Is Your Infrastructure Affected by CVE-2026-73064?

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

Book a Demo →Browse All CVEs