VulertSecurity VulertSecurity

Vulnerability Database · Alpine · Package report

mbedtls: vulnerability history, versions and safety

mbedtls is a package in the Alpine ecosystem. Vulert records 25 vulnerabilities for it across 48 releases, from Sep 2024 to Apr 2026. Each vulnerability names the versions it affects, the fixed version to move to, and a workaround where no fix has been published.

i
25 vulnerabilities recorded U25
i
0 with no fix published

Every vulnerability has a patched version to move to.

i
3 in the last 12 months

Most recent disclosure 01 Apr 2026.

See the disclosure history →
i
0 malicious-package vulnerabilities

No published version shipped hostile code.

See all mbedtls vulnerabilities

Vulert verdict on mbedtls i

Updated on 23 Oct 2026

Every vulnerability Vulert records for this package has a fix, and the newest was recorded 01 Apr 2026. Apply the fixes listed below and you are clear.

Long-term outlook: usable, with an upgrade 25 vulnerabilities on record across 1 year, 3 in the last year.

What to do: Move the affected dependencies to the fixed versions listed below, then keep the package monitored so the next vulnerability reaches you. Fix it, then keep watch: Vulert alerts you when a new vulnerability affects the version you run. Monitor it with Vulert →

  • Vulnerabilities on record 25 over 1 year · 3 in the last year i
  • Latest disclosure 01 Apr 2026 i
  • Highest CVSS 9.8 i
  • With no published fix 0 i

Concerned about your application's security?

Vulert continues monitoring your dependencies and alerts you when new vulnerabilities are disclosed. No installation and no source-code access required.

01 Versions

Which versions are affected

Every version Vulert holds for mbedtls, newest first, with the vulnerabilities that name it. A version with a count of zero has no recorded vulnerabilities; open a version to see the vulnerabilities it is exposed to.

Newest 48 of 48 versions on record. Severity counts are the vulnerabilities recorded against that exact release.

02 Disclosure history

How often vulnerabilities are recorded

  • 2024 6
  • 2025 16
  • 2026 3

Counted by the year Vulert recorded each vulnerability — the same date the table below shows as disclosed. 3 of the 25 were recorded in the last 12 months.

03 Vulnerabilities

Recorded vulnerabilities for mbedtls

The 5 most severe of 25 vulnerabilities recorded for this package

Search all 25 in the database →
Vulnerability Severity Fixed version ↓ Disclosed ↓
Vulnerability in Mbed TLS 3.x before 3.6.1 9.8 critical 3.6.1-r0 05 Sep 2024
Critical Vulnerability in Mbed TLS: Insecure Client Certificate Authentication 9.8 critical 3.6.1-r0 05 Sep 2024
Critical Use-After-Free Vulnerability in Mbed TLS Package 9.8 critical 3.6.4-r0 20 Jul 2025
Use-After-Free Vulnerability in Mbed TLS: CVE-2025-47917 9.8 critical 3.6.4-r0 20 Jul 2025
Race Condition Vulnerability in Mbed TLS: AES Key Extraction Risk 7.8 high 3.6.4-r0 04 Jul 2025

Vulnerability wrong, a fix missing, or a package we should cover? Report it and we will fix the record. Report Vulnerability Provide Feedback

Updated: 23/Oct/2026 · Vulnerabilities in our DB: 524315

Subscribe to Vulert on Telegram
Daily digest of new CVEs, critical and high severity, affected packages and fixes — plus a weekly roundup.
Join the channel →

Questions

About mbedtls

Is mbedtls safe to use?

Vulert records 25 vulnerabilities for mbedtls in Alpine: 0 critical, 0 high, 0 medium and 0 low, plus 25 not yet rated. Every one of them has a published fix, so the practical answer is to run a supported release and keep it patched.

How many vulnerabilities does mbedtls have?

25 vulnerabilities are recorded for mbedtls in the Alpine ecosystem: 0 critical, 0 high, 0 medium and 0 low, plus 25 not yet rated. The ledger on this page lists the same counts next to the date of the most recent disclosure.

How often are new mbedtls vulnerabilities disclosed?

3 vulnerabilities were recorded for mbedtls in the last 12 months, and the oldest entry in this database dates to 05 Sep 2024. Recency matters more than a lifetime total: it shows how actively new issues are being disclosed for the package you are considering.

Which versions of mbedtls are affected?

Each vulnerability on this page lists the affected version range and the fixed version to move to. Open the vulnerability for the version you actually run — fixes are specific to a release line, not to the package as a whole.

How do I monitor mbedtls for upcoming vulnerabilities?

Upload the manifest or SBOM for your application at vulert.com/scanner and Vulert keeps checking the mbedtls version you actually run against new disclosures, then alerts you when one affects it. There is no installation and no source-code access required.