Mbed TLS
Security status for teams that ship Mbed TLS: which branches get fixes and for how long, every advisory, and the fixes a given version is missing.
Mbed TLS has 3 maintained branches, and support for 3.6 LTS ends in March 2027, less than six months away. 89 CVEs are on record and 28 were fixed in 2026 releases. None is known to be exploited (CISA KEV, 10 Nov 2026).
19 CVEs have no NVD score yet. MCUboot and U-Boot ship 3.6.0, which is missing 42 security fixes.
Check a version
Pick the Mbed TLS version in your product to see the security fixes released after it on its branch, and what to move to.
Support runway
How long each branch gets security fixes. A product that must be supported beyond a branch's end date cannot rely on that branch.
Advisories 89
Every CVE in Mbed TLS, PolarSSL and TF-PSA-Crypto. Severity is NVD's base score; unscored means NVD has not published one yet.
Who ships which Mbed TLS
Default branch of each project, checked 11 Nov 2026. Forks may carry backported fixes that a version number does not show.
The Cyber Resilience Act and your Mbed TLS
What the regulation expects of a manufacturer that ships Mbed TLS, and where this page answers it. A summary, not legal advice.
Report actively exploited vulnerabilities
Since 11 Sep 2026: early warning within 24 hours, through ENISA's Single Reporting PlatformNone is known to be exploited: no Mbed TLS CVE is in the CISA known exploited catalogue (10 Nov 2026).
Ship without known exploitable vulnerabilities
Essential requirement, from 11 Dec 2027Check your version above for every security fix released after it.
Handle vulnerabilities in components
Including an SBOM and a record of what you assessedThe missing-fix list for your version is the list to assess.
Security updates for the support period
At least five years, unless the product is in use for lessThe support runway shows where your Mbed TLS branch runs out.