CVE-2026-73064 json
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…
published last mo. modified last mo. also EUVD-2026-85930
- cvss
- 2.9
- version 3.1, CNA
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 0.1%
- EPSS 0.1% chance of exploitation in 30 days, percentile 0%
- public exploits
- 0
- none known
Summary
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.
Patch / fix
- trustedfirmware Mbed TLS 3.6.7, 4.1.1
- mbedtls Debian 14 3.6.7-1
debian advisories DEBIAN-CVE-2026-73064
Is CVE-2026-73064 in your stack? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.
Check with FencerVendor advisories
What the vendors themselves say about their products: affected, fixed or not affected, and what to do.
red hat product security vex CVE-2026-73064 updated
mbedtls: Mbed TLS: TLS stream integrity compromise via entropy source failure
-
Red Hat All currently supported Red Hat productsnot affected: vulnerable code not present
Red Hat CSAF VEX © Red Hat, Inc., from https://security.access.redhat.com/data/csaf/v2/vex/; changed: reduced to product statuses and remediations. CC BY 4.0 · csaf
CISA SSVC
- Exploitation
- none
- Automatable
- no
- Technical impact
- partial
- Assessed
- last mo.
Exploit prediction
0.10% chance of exploitation in the next 30 days, higher than 0% of all scored CVEs (FIRST EPSS, 2026-11-11).
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| CNA | 3.1 | 2.9 | CVSS:3.1/AV:L/AC:H/PR:N/UI:N/S:U/C:N/I:L/A:N |
Affected products
- trustedfirmware Mbed TLS
Classification
- Weakness
-
- CWE-394 Unexpected Status Code or Return Value
References
Sources
- CVE List CVE-2026-73064
- NVD CVE-2026-73064
Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.