nday
CVE-2025-49600

Mbed mbedtls: cryptographic failureTitle composed by nday; the CVE record has none.

Mbed / mbedtls

Disclosed . nday has no fix record for it yet; that does not mean no patch exists. None of the four PoC sources lists it. Not in CISA KEV.

why these tags

nday derives these tags by fixed rules from the facts below; NVD, the CNA and other sources do not assign them. Vocabulary and rules: ~/tags.

cryptographic failure
CWE-325, stated by the CNA mitre and NVD, republishing [email protected]
physical
AV:P in CVSS:3.1/AV:P/AC:H/PR:N/UI:N/S:C/C:N/I:H/A:N (CVSS 3.1) from the CNA mitre
no authentication required
PR:N in CVSS:3.1/AV:P/AC:H/PR:N/UI:N/S:C/C:N/I:H/A:N (CVSS 3.1) from the CNA mitre
no user interaction
UI:N in CVSS:3.1/AV:P/AC:H/PR:N/UI:N/S:C/C:N/I:H/A:N (CVSS 3.1) from the CNA mitre
stage
DIS
disclosed
cvss
4.9 MEDIUM v3.1

Lifecycle

x axis UTC; dot = exact minute, wide bar = date only, hollow = unknown or inferred.
time unknown
DISdisclosed
2025-07-04T00:00Z
PATpatch
no record yet
ANAanalysis
no record yet
POCPoC
no record yet
ITWexploited
no record yet
KEVKEV
no record yet

Summary

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.

Original text of the CVE record (cvelist), shown as published.

Exploit conditions

What an attack needs, read from the CVSS vector.
Attack vector AV:P
Physical: needs physical access to the device
Attack complexity AC:H
High: success depends on conditions outside the attacker's control, such as gathering details of the target or winning a race
Privileges required PR:N
None: no account or authorization needed
User interaction UI:N
None: no action by anyone other than the attacker

CVSS:3.1/AV:P/AC:H/PR:N/UI:N/S:C/C:N/I:H/A:N

CVSS 3.1 vector from the CVE record, scored by the CNA mitre.

Event log

+DISdisclosed

CVE record published by mitre. CVSS 4.9, medium.

src cvelist · nday , bulk import · raw
{
  "id": 380427,
  "type": "disclosed",
  "source": "cvelist",
  "url": "https://www.cve.org/CVERecord?id=CVE-2025-49600",
  "occurred_at": "2025-07-04T00:00:00Z",
  "observed_at": "2026-11-13T05:39:11.210681Z",
  "is_backfill": true,
  "dedupe_key": "",
  "detail": {
    "cvss": {
      "source": "cna",
      "vector": "CVSS:3.1/AV:P/AC:H/PR:N/UI:N/S:C/C:N/I:H/A:N",
      "version": "3.1",
      "base_score": 4.9,
      "base_severity": "MEDIUM"
    },
    "ssvc": {
      "timestamp": "2025-07-08T13:18:22.211877Z",
      "automatable": "no",
      "exploitation": "none",
      "technical_impact": "partial"
    },
    "state": "PUBLISHED",
    "date_published": "2025-07-04T00:00:00.000Z",
    "assigner_short_name": "mitre"
  }
}

Report an error

report an error or omission

Something on this page wrong or missing? Tell the editors; if they accept it, this page's revision log says so publicly. Upstream data is not changed.

Researcher discussion

0 researchers mentioned this in the last 7 days

Posts on X by researchers on nday's list that mention this CVE, shown as posted. nday does not check them.

nday has not collected any post on X by listed researchers that mentions this CVE.

Discussion

0 comments

No comments yet.