Linux ·
Ubuntu · Package update · July 20, 2025
Ubuntu · Package update · July 20, 2025libmbedcrypto1 2.8.0-1ubuntu0.1~esm1: libmbedcrypto1 2.8.0-1ubuntu0.1~esm1 for Ubuntu 18.04.6 LTS (bionic)
libmbedcrypto1 2.8.0-1ubuntu0.1~esm1, released July 20, 2025, fixes 7 CVEs in libmbedcrypto1. None of them is reported as exploited. Patch Radar priority: Urgent. The product is no longer supported.
UrgentUnsupported product
CVEs closed
7
2 rated Critical
Exploited
0
None reported
Highest CVSS
9.8
Base score, 0 to 10
Highest EPSS
0.0277
86th percentile
Priority of the 7 CVEs
Patch now 0
Urgent 2
High 3
Routine 2
Fixed package versions
| Product | Release | Fixed in |
|---|---|---|
| libmbedcrypto1 | Ubuntu 18.04.6 LTS (bionic) | 2.8.0-1ubuntu0.1~esm1 |
CVEs this fix closes
| Priority | CVE | Title | CVSS | EPSS | Exploitation |
|---|---|---|---|---|---|
| Urgent | CVE-2021-44732 | mbedtls: Mbed TLS before 3.0.1 has a double free in certain out-of-memory conditions, as demonstrated by an mbedtls_ssl_set_se... | 9.8 | 0.0277 | None reported |
| Urgent | CVE-2025-47917 | mbedtls: (boo#1246783): misleading memory management in | 9.8 | 0.0244 | None reported |
| High | CVE-2024-23775 | libmbedx509-1: Integer Overflow vulnerability in Mbed TLS 2.x before 2.28.7 and 3.x before 3.5.2, allows attackers to cause a denial... | 7.5 | 0.0111 | None reported |
| High | CVE-2025-48965 | mbedtls: (boo#1246784): NULL pointer dereference after | 7.5 | 0.0057 | None reported |
| High | CVE-2025-52496 | Mbed TLS before 3.6.4 has a race condition in AESNI detection if certain compiler optimizations occur. An attacker may be able to extract an AES key from a multithreaded program, or perform a GCM forgery. | 7.8 | 0.0021 | None reported |
| Routine | CVE-2025-52497 | mbedtls: (boo#1245811): one-byte heap underflow when parsing | 4.8 | 0.0033 | None reported |
| Routine | CVE-2025-27810 | mbedtls: (boo#1240052): possible authentication bypass on | 4.8 | 0.0030 | None reported |
Showing 1 to 7 of 7
1
Patch Radar data is free to use with attribution. Terms and how to credit it.
Product names, logos and trademarks shown on Patch Radar belong to their respective owners. They are used only to identify the software each security fix applies to and to help readers find their platform. Their use does not imply any affiliation with, or endorsement by, those owners, and Patchblox is not affiliated with any of them.