Related Threat Clusters
-
Critical Mbed TLS Vulnerabilities Affect Multiple Ubuntu Releases
Multiple vulnerabilities have been identified in Mbed TLS, impacting Ubuntu 18.04 LTS, 20.04 LTS, 22.04 LTS, and 24.04 LTS. The vulnerabilities include improper handling of memory allocation failures (CVE-2021-44732),…
2 articles · Updated March 25, 2026 -
Vulnerabilities Discovered in Mbed TLS Affecting Certificate Validation and Memory Security
Two vulnerabilities were identified in Mbed TLS, affecting versions prior to 2.25.0 and 2.24.0. CVE-2020-36478 allows a NULL algorithm parameters entry to be misinterpreted as valid, while CVE-2020-36476 involves…
9 articles · Updated February 18, 2026 -
Vulnerabilities in Arm Mbed Crypto and Mbed TLS Expose Private Keys
Two vulnerabilities have been identified in Arm Mbed Crypto and Mbed TLS that could allow local attackers to recover private keys through side-channel attacks. CVE-2019-18222, published on January 23, 2020, involves an…
3 articles · Updated February 18, 2026 -
Multiple Vulnerabilities Found in Mbed TLS Affecting Key Security
Two vulnerabilities have been identified in Mbed TLS that could allow attackers to extract sensitive cryptographic keys. CVE-2020-10941, published on March 24, 2020, enables attackers to obtain RSA private keys through…
7 articles · Updated February 18, 2026
Recent Intelligence Reports
- USN-8123-1: Mbed TLS vulnerabilities — Ubuntu · March 25, 2026
- CVE-2019-18222 The ECDSA signature implementation in ecdsa.c in Arm Mbed Crypto 2.1 and Mbed TLS through 2.19.1 does not reduce the blinded scalar before computing the inverse, which allows a local attacker to recover the private key via side — Api.Msrc.Microsoft · February 18, 2026
- CVE-2025-27810 Mbed TLS before 2.28.10 and 3.x before 3.6.3, in some cases of failed memory allocation or hardware errors, uses uninitialized stack memory to compose the TLS Finished message, potentially leading to authentication bypasses such as replays. — Api.Msrc.Microsoft · February 18, 2026
- CVE-2020-36475 An issue was discovered in Mbed TLS before 2.25.0 (and before 2.16.9 LTS and before 2.7.18 LTS). The calculations performed by mbedtls_mpi_exp_mod are not limited; thus, supplying overly large parameters could lead to denial of service when generating Diffie — Api.Msrc.Microsoft · February 18, 2026
- CVE-2020-36477 An issue was discovered in Mbed TLS before 2.24.0. The verification of X.509 certificates when matching the expected common name (the cn argument of mbedtls_x509_crt_verify) with the actual certificate name is mishandled: when the subjecAltName extension is present, the expected name is compared to any name in that extension regardless of its type. This means that an attacker could impersonate a 4-byte or 16-byte domain by getting a certificate for the corresponding IPv4 or IPv6 address (this would require the attacker to control that IP address, though). — Api.Msrc.Microsoft · February 18, 2026
- CVE-2020-36478 An issue was discovered in Mbed TLS before 2.25.0 (and before 2.16.9 LTS and before 2.7.18 LTS). A NULL algorithm parameters entry looks identical to an array of REAL (size zero) and thus the certificate is considered valid. However, if the parameters do not match in any way, then the certificate should be considered invalid. — Api.Msrc.Microsoft · February 18, 2026
- CVE-2025-27809 Mbed TLS before 2.28.10 and 3.x before 3.6.3, on the client side, accepts servers that have trusted certificates for arbitrary hostnames unless the TLS client application calls mbedtls_ssl_set_hostname. — Api.Msrc.Microsoft · February 18, 2026
- CVE-2021-44732 Mbed TLS before 3.0.1 has a double free in certain out-of-memory conditions, as demonstrated by an mbedtls_ssl_set_session() failure. — Api.Msrc.Microsoft · February 18, 2026