Skip to main content
CVE-2026-73064VulnerabilityPublished Updated

Microsoft · 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

Affects MicrosoftSource GCVE Database

0
Compare
Authoritative record:CVE-2026-73064· Low 2.9

Not known to be exploited · CVSS 2.9 Low : upgrade to 4.1.1 or 3.6.7 when convenient.

Data as of 17 Nov 2026, 10:20 UTC

CVSS 3.1 base score
2.9Low
How severe the flaw is on the 0–10 CVSS scale.
Patch
Available – fixed in 4.1.1, 3.6.7
CVSS:3.1/AV:L/AC:H/PR:N/UI:N/S:U/C:N/I:L/A:N

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 24 Sep 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponized: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 16 Nov 2026.

What to do

Upgrade Mbed TLS to 4.1.1 or 3.6.7.

Affected software

ProductAffectedFixed in
trustedfirmwareMbed TLSAffected
  • >=4.0.0 <4.1.1
Fixed in
  • 4.1.1
trustedfirmwareMbed TLSAffected
  • >=3.2.0 <3.6.7
Fixed in
  • 3.6.7
GitHubMbed TLSpkg:github/Mbed TLSOther threatsAffected
  • >=3.2.0 <3.6.7
  • >=4.0.0 <4.1.1
Fixed in
  • 3.6.7
  • 4.1.1

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

Description

To determine the support lifecycle for your software, see the Microsoft Support Lifecycle: https://support.microsoft.com/lifecycle

References

Community reviews

Loading reviews…