CVE-2025-27810 Details
Description
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.
A vulnerability exists in Mbed TLS versions prior to 2.28.10 and 3.x prior to 3.6.3. In certain situations where memory allocation fails or hardware errors occur, the library improperly uses uninitialized stack memory to create the TLS Finished message. This flaw can disrupt the TLS handshake process, potentially allowing an attacker to tamper with the handshake or replay messages to impersonate a legitimate peer.
Users should upgrade to Mbed TLS 3.6.3 or Mbed TLS 2.28.10.
Metrics
CVSS 4.0 Severity and Vector Strings:
No CVSS 4.0 data is available for this CVE.
CVSS 3.x Severity and Vector Strings:
No data available for CVSS Version 2.0 on this CVE.
CISA-ADP
Assessed Mar 25, 2025References to Advisories, Solutions, and Tools
By selecting these links, you will be leaving this site. These are references gathered from the official CVE record and are not endorsed by Volerion.
| URL | Source(s) | Tag(s) |
|---|---|---|
| https://github.com/Mbed-TLS/mbedtls/releases | [email protected] | Release Notes |
| https://mbed-tls.readthedocs.io/en/latest/security-advisories/mbedtls-security-advisory-2025-03-2/ | [email protected] | Vendor Advisory |
Weakness Enumeration
| CWE-ID | CWE Name | Source |
|---|---|---|
| CWE-908 | Use of Uninitialized Resource | [email protected] |
Affected Products
| Product | Versions |
|---|---|
| arm mbed tls | < 2.28.10 |
CPE
Remediation
| |
| trustedfirmware mbed tls | >= 3.0.0, < 3.6.3 |
CPE
Remediation
| |
Change History
5 change records found show changes
| Date | Action | Recorded By |
|---|---|---|
| Jun 17, 2026 | CVE Modified | [email protected] |
| Jun 17, 2026 | CVE Modified | CISA-ADP |
| Jun 5, 2026 | CPE Deprecation Remap | [email protected] |
| Oct 30, 2025 | Initial Analysis | [email protected] |
| Mar 25, 2025 | New CVE Received | [email protected] |