CVE-2025-49601: Medium severity MbedTLS MbedTLS vulnerability
In MbedTLS 3.3.0 before 3.6.4, mbedtlslmsimportpublickey does not check that the input buffer is at least 4 bytes before reading a 32-bit field, allowing a possible out-of-bounds read on truncated input. Specifically, an out-of-bounds read in mbedtlslmsimportpublickey allows context-dependent attackers to trigger a crash or limited adjacent-memory disclosure by supplying a truncated LMS (Leighton-Micali Signature) public-key buffer under four bytes. An LMS public key starts with a 4-byte type indicator. The function mbedtlslmsimportpublickey reads this type indicator before validating the size of its input.
Affected Software
Event History
Frequently Asked Questions
What is the severity of CVE-2025-49601?
CVE-2025-49601 is classified as a potential security vulnerability due to the risk of an out-of-bounds read in affected versions of MbedTLS.
How do I fix CVE-2025-49601?
To fix CVE-2025-49601, upgrade MbedTLS to version 3.6.4 or later as this version contains the necessary security patches.
Which versions of MbedTLS are affected by CVE-2025-49601?
MbedTLS versions 3.3.0 through 3.6.3 are affected by CVE-2025-49601.
What type of vulnerability is CVE-2025-49601?
CVE-2025-49601 is categorized as an out-of-bounds read vulnerability that can lead to undefined behavior in the application.
Is there any workaround for CVE-2025-49601?
There are no officially recommended workarounds for CVE-2025-49601 other than upgrading to the secure version of MbedTLS.