cve.bz

CVE-2025-49600 trustedfirmware mbed tls: Missing Cryptographic Step

4.9 mediumEPSS 0.2%

Medium (4.9) in trustedfirmware mbed tls. EPSS 0.2% estimated probability of exploitation activity in the next 30 days.

On this page
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.

Severity

CVSS 3.1

4.9 medium
CVSS:3.1/AV:P/AC:H/PR:N/UI:N/S:C/C:N/I:H/A:N
EPSS
0.2% (unchanged from 0.2% a week ago; 0.2% 30 days ago) estimated probability of exploitation activity in the next 30 days; 5th percentile. Scored 2026-11-22. A forecast for this CVE across the internet, not for your own systems.
CISA's assessment (SSVC)
Exploitation: none · Automatable: no · Technical impact: partial, assessed 2025-07-08. From CISA's Vulnrichment in the CVE List: whether it is exploited, whether exploiting it can be automated, and how much control it gives.
CWE
CWE-325 Missing Cryptographic Step
OWASP Top 10
A04:2025 Cryptographic Failures
Published
Modified
NVD analysis
Analyzed
Record from
the NVD, synced

Fix and patched versions

Ask an AI about this CVE

Show the promptExplain CVE-2025-49600 for an engineer deciding whether to act. Use https://cve.bz/api/public/cves/CVE-2025-49600?via=ask-ai-copy and https://cve.bz/cve/CVE-2025-49600?via=ask-ai-copy as the source of truth: what is affected and which versions fix it, whether it is in CISA KEV, public exploits, and its EPSS (an internet-wide 30-day estimate of exploitation activity, not a forecast for my systems). If they give no fixed versions, use the CVE record https://cveawg.mitre.org/api/cve/CVE-2025-49600 or the vendor advisory, not third-party mirrors. Tell me how to check whether I am affected and how to verify a fix. Cite the sources and say where they are uncertain.

Opens a third-party assistant; its answer is its own, not cve.bz's. The prompt holds only this CVE's id and public links.

Affected

Versions

From the CNA's record in the CVE List.

ProductAffected
mbedtlsfrom 3.3.0 before 3.6.4

Linux distributions

DistributionReleasePackageFixed inAdvisory
Debian13, 14mbedtls3.6.4-1DEBIAN-CVE-2025-49600
Ubuntu25.10, 26.04:LTSmbedtlsno fix listedUBUNTU-CVE-2025-49600
openSUSELeap 16.0mbedtls3.6.6-bp160.1.1openSUSE-SU-2026:21144-1
Alpinev3.20, v3.21, v3.22 and 1 morembedtls3.6.4-r0ALPINE-CVE-2025-49600
Alpinev3.24mbedtls, mbedtls33.6.4-r0ALPINE-CVE-2025-49600

From the distributions' data via OSV.dev: the Debian Security Tracker; Ubuntu Security Notices © Canonical Ltd., CC BY-SA 4.0; SUSE security data, CC BY 4.0; the Alpine secdb, CC BY-SA 4.0. Modified: reformatted and linked to CVE records. Credits. On the distributions' own pages: Debian · Ubuntu · openSUSE · Alpine.

Attack patterns (CAPEC)

  • CAPEC-68 Subvert Code-signing Facilities Likelihood: Low · Severity: Very High

The attack patterns MITRE's CAPEC relates to this record's weaknesses, as MITRE names them. Credits.

References

Check your stackJSON