Signature forgery via unchecked hash failures
Published Jul 4, 2025 · Updated Jul 8, 2025
LMS signature verification in Mbed TLS 3.3.0 through 3.6.3 allows physically proximate attackers to make invalid signatures pass. The mbedtls_lms_verify function ignores failures from create_merkle_leaf_value and create_merkle_internal_value, leaving a prior root value on the stack. Exploitation requires fault injection against a hardware hash accelerator after a valid check and permits a changed message to reuse the valid signature; software SHA-256 is unaffected.
Summary
What happened
LMS signature verification in Mbed TLS 3.3.0 through 3.6.3 allows physically proximate attackers to make invalid signatures pass. The mbedtls_lms_verify function ignores failures from create_merkle_leaf_value and create_merkle_internal_value, leaving a prior root value on the stack. Exploitation requires fault injection against a hardware hash accelerator after a valid check and permits a changed message to reuse the valid signature; software SHA-256 is unaffected.
The record
- CVE
- CVE-2025-49600
- Published
- Jul 4, 2025
- Updated
- Jul 8, 2025
- Vendor
- TrustedFirmware.org
- Product
- Mbed TLS
- Classifications
- CWE-325
- Attack vector
- physical
- Privileges
- unauthenticated
Timeline
How it unfolded
- Jul 4, 2025CVE publishedPublication date reported by the CVE source.
- Jul 8, 2025Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=3.3.0 <3.6.4
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo