CVE-2025-59438 Details
Description
Mbed TLS through 3.6.4 has an Observable Timing Discrepancy.
A padding oracle vulnerability has been identified in Mbed TLS versions prior to 3.6.4. This vulnerability arises from an observable timing discrepancy in the decryption process of ciphertexts with padding, particularly in CBC-PKCS7 mode. When the PSA Crypto API is used, the error handling is not constant-time, allowing local attackers to infer information about the plaintext or recover secret parts by exploiting the timing of error reports. While the legacy API can be vulnerable depending on how errors are managed, the main risk lies in the PSA API when using the built-in CBC-PKCS7 implementation.
Users should upgrade to Mbed TLS 3.6.5 or later. For applications using the legacy API, review error handling when decrypting with CBC or ECB modes that include padding, and consider switching to `mbedtls_cipher_finish_padded()`, which simplifies the management of invalid-padding errors. Applications using the PSA Crypto API with `PSA_ALG_CBC_PKCS7` should handle errors carefully to mitigate the risk of local timing attacks.
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 Oct 21, 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.
Weakness Enumeration
| CWE-ID | CWE Name | Source |
|---|---|---|
| CWE-208 | Observable Timing Discrepancy | CISA-ADP |
Affected Products
| Product | Versions |
|---|---|
| arm mbed tls | < 3.6.5 |
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 |
| Oct 23, 2025 | Initial Analysis | [email protected] |
| Oct 21, 2025 | CVE Modified | CISA-ADP |
| Oct 21, 2025 | New CVE Received | [email protected] |