CVE-2025-27810: Medium severity Mbed TLS Mbed TLS vulnerability
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.
Affected Software
Remediation
Recommended actions to resolve this vulnerability, in priority order.
- Upgrade
Upgrade
alpine/mbedtlsto a version that resolves this vulnerability.Fixed in 2.28.10-r0 - Upgrade
Upgrade
alpine/mbedtlsto a version that resolves this vulnerability.Fixed in 3.6.3-r0 - Upgrade
Upgrade
alpine/mbedtls2to a version that resolves this vulnerability.Fixed in 2.28.10-r0 - Upgrade
Upgrade
alpine/mbedtls3to a version that resolves this vulnerability.Fixed in 3.6.3-r0
Event History
Frequently Asked Questions
What is the severity of CVE-2025-27810?
CVE-2025-27810 is classified as a moderate severity vulnerability due to its potential for authentication bypass.
How do I fix CVE-2025-27810?
To fix CVE-2025-27810, upgrade to Mbed TLS version 2.28.10 or later, or 3.6.3 or later.
What types of issues can CVE-2025-27810 cause?
CVE-2025-27810 can cause authentication bypasses, which may allow for replay attacks.
Which versions of Mbed TLS are affected by CVE-2025-27810?
CVE-2025-27810 affects Mbed TLS versions prior to 2.28.10 and 3.x versions prior to 3.6.3.
What specific condition triggers CVE-2025-27810?
CVE-2025-27810 is triggered by failed memory allocation or hardware errors during TLS message composition.