CVE-2025-27809: Medium severity Arm mbed TLS vulnerability
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 mbedtlssslsethostname.
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-27809?
CVE-2025-27809 is considered a high severity vulnerability due to the potential for man-in-the-middle attacks.
How do I fix CVE-2025-27809?
To fix CVE-2025-27809, ensure that the mbedtls_ssl_set_hostname function is called in your TLS client application.
Which versions of Mbed TLS are affected by CVE-2025-27809?
CVE-2025-27809 affects Mbed TLS versions before 2.28.10 and 3.x before 3.6.3.
What impact does CVE-2025-27809 have on TLS connections?
CVE-2025-27809 allows TLS clients to trust servers based on arbitrary hostnames, which can lead to security risks.
Is there a patch available for CVE-2025-27809?
Yes, patches for CVE-2025-27809 are available in Mbed TLS versions 2.28.10 and 3.6.3 and later.