{"schemaVersion":1,"url":"https://cve.openhack.com/cve/CVE-2025-49600","id":"CVE-2025-49600","title":"In MbedTLS 3.3.0 before 3.6.4, mbedtls_lms_verify may accept invalid signatures if hash computation fails and interna…","description":"In MbedTLS 3.3.0 before 3.6.4, mbedtls_lms_verify may accept invalid signatures if hash computation fails and internal errors go unchecked, enabling LMS (Leighton-Micali Signature) forgery in a fault scenario. Specifically, unchecked return values in mbedtls_lms_verify allow an attacker (who can induce a hardware hash accelerator fault) to bypass LMS signature verification by reusing stale stack d","descriptionLong":"In MbedTLS 3.3.0 before 3.6.4, mbedtls_lms_verify may accept invalid signatures if hash computation fails and internal errors go unchecked, enabling LMS (Leighton-Micali Signature) forgery in a fault scenario. Specifically, unchecked return values in mbedtls_lms_verify allow an attacker (who can induce a hardware hash accelerator fault) to bypass LMS signature verification by reusing stale stack data, resulting in acceptance of an invalid signature. In mbedtls_lms_verify, the return values of the internal Merkle tree functions create_merkle_leaf_value and create_merkle_internal_value are not checked. These functions return an integer that indicates whether the call succeeded or not. If a failure occurs, the output buffer (Tc_candidate_root_node) may remain uninitialized, and the result of the signature verification is unpredictable. When the software implementation of SHA-256 is used, these functions will not fail. However, with hardware-accelerated hashing, an attacker could use fault injection against the accelerator to bypass verification.","published":"2025-07-04T00:00:00.000Z","updated":"2026-10-28T02:31:00.206646109Z","reserved":"2025-06-06T00:00:00.000Z","status":"Analyzed","rejected":false,"assigner":"mitre","metric":{"version":"3.1","score":4.9,"vector":"CVSS:3.1/AV:P/AC:H/PR:N/UI:N/S:C/C:N/I:H/A:N","rating":"medium","source":"mitre"},"metrics":[{"version":"3.1","score":4.9,"vector":"CVSS:3.1/AV:P/AC:H/PR:N/UI:N/S:C/C:N/I:H/A:N","rating":"medium","source":"mitre"},{"version":"3.1","score":4.9,"vector":"CVSS:3.1/AV:P/AC:H/PR:N/UI:N/S:C/C:N/I:H/A:N","rating":"medium","source":"mitre.org"},{"version":"3.1","score":4.9,"vector":"CVSS:3.1/AV:P/AC:H/PR:N/UI:N/S:C/C:N/I:H/A:N","rating":"medium","source":"OSV"}],"rating":"medium","products":["mbedtls"],"affectedProducts":[{"vendor":"Mbed","product":"mbedtls","defaultStatus":"unaffected","versions":[{"lessThan":"3.6.4","status":"affected","version":"3.3.0","versionType":"custom"}],"platforms":[]}],"packages":[],"cwes":["CWE-325"],"aliases":[],"references":[{"url":"https://github.com/Mbed-TLS/mbedtls-docs/blob/main/security-advisories/mbedtls-security-advisory-2025-06-3.md","tags":["Third Party Advisory","advisory"]},{"url":"https://github.com/CVEProject/cvelistV5/tree/main/cves/2025/49xxx/CVE-2025-49600.json","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-49600","tags":["advisory"]}],"patchReferenced":false,"fixAvailable":false,"exploitReferenced":false,"kev":false,"kevAdded":null,"kevDue":null,"kevEntry":null,"ssvc":{"exploitation":"none","automatable":"no","technicalImpact":"partial"},"epss":0.00158,"epssPercentile":0.05048,"sources":[{"name":"CVE List","url":"https://www.cve.org/CVERecord?id=CVE-2025-49600","ok":true},{"name":"NVD","url":"https://nvd.nist.gov/vuln/detail/CVE-2025-49600","ok":true,"note":"Analyzed"},{"name":"OSV","url":"https://osv.dev/vulnerability/CVE-2025-49600","ok":true,"note":"0 packages"},{"name":"CISA KEV","url":"https://www.cisa.gov/known-exploited-vulnerabilities-catalog","ok":true,"note":"not listed"},{"name":"EPSS","url":"https://api.first.org/data/v1/epss?cve=CVE-2025-49600","ok":true,"note":"scored 2026-11-18"}],"aiTitle":false,"tech":[],"critical":[],"attention":null}