Skip to main content
Menu
CVEs

CVE

libspdm certificate constraint bypass in X.509 chain verification

CVE-2026-129306EUVD-2026-126576

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

4.4MediumCNA
Exploited
No known exploitation
Fix
Fixed in 3.8.3, 4.0.0-rc2
Who is exposed
Not reported

Do first: Upgrade to a fixed version: 3.8.3, 4.0.0-rc2.

Published
Last modified
Reference
Last checked
7/100 · provisional
None on Exploit-DB, Metasploit or GitHub
  • Exploitation: none
  • Automatable: no
  • Technical impact: partial

Summary

DMTF libspdm, a sample implementation of the SPDM specifications, checks certificate signatures one link at a time instead of validating the full chain. A remote attacker who already holds a valid credential below a constrained certificate authority can get a subordinate certificate that breaks that authority's path length or name constraints accepted for identity validation, which requires high privileges to reach over the network.

Written by anthropic/claude-haiku-5.5 from the sources below. Verify against them.

Original description

libspdm is a sample implementation that follows the DMTF SPDM specifications. Prior to 3.8.3 and 4.0.0-rc2, libspdm_x509_verify_cert_chain() in os_stub/cryptlib_openssl/pk/x509.c and os_stub/cryptlib_mbedtls/pk/x509.c validates certificate signatures one link at a time instead of validating the complete X.509 path. In deployments using a pinned root with a constrained multi-tier PKI, an attacker holding a valid issuer credential below a constrained CA can present a subordinate certificate that exceeds pathLenConstraint or nameConstraints and may be accepted for SPDM identity validation. Exploitation requires the application to use libspdm's backend validation without an additional certificate-chain validation mechanism, the pinned root cannot be substituted, and the deployment's measurement policy must allow identity impersonation alone to satisfy its acceptance requirements. The mbedTLS backend remains unable to enforce nameConstraints because upstream mbedTLS does not implement that check. The full-chain validation changes are released in versions 3.8.3 and 4.0.0-rc2.

cve.now Index

7Pcve.now Index 7 of 100 · methodology v3 · provisional
  • Exploitation0/40No signal
  • Exposure3/25Reachable over the network · Unknown: No advisory context yet
  • Reach?/20Unknown. No tracked technology or package matched
  • Severity4.4/10CVSS 4.4
  • No patch0/5No signal

What would change the score

  • Would score about 62 if added to CISA KEV
  • Would score about 57 if CISA's SSVC rates exploitation active
  • Would score about 26 if advisories confirm default setups are exposed

What to do

  • Upgrade to a fixed version: 3.8.3, 4.0.0-rc2.

Check your systems with an agent

Paste this into a coding or ops agent. It checks your systems read-only and reports a table per asset.

Check whether my systems are affected by CVE-2026-129306 (libspdm: libspdm_x509_verify_cert_chain() does not verify CA nameConstraints / pathLenConstraint), using the cve.now data below.

Rules: work read-only. Do not run exploit code, proof-of-concept scripts or scanners that send attack payloads, and do not change any configuration, package, image or deployment. Report findings only.

What cve.now has for CVE-2026-129306 (entry last updated 2026-11-16):
Affected:
- DMTF libspdm: fixed in 3.8.3; from 4.0.0-rc1, fixed in 4.0.0-rc2
Fixed versions: 3.8.3, 4.0.0-rc2.
Setup: unknown whether the bug needs a non-default feature or setting. Check the advisory.
CISA KEV: CVE-2026-129306 is not listed as of cve.now's last read.
This KEV status is for CVE-2026-129306 only. If you also check another CVE, look up its own KEV status; never assume it from this one.

How to check:
- Installed software: check what is actually running, not what a repo declares. Read the version from each host, container image and Kubernetes node (the binary's version output, the OS package database, image layers), and check whether the conditions above hold there. Distribution packages may carry a backported fix under an older version number; confirm against the distribution's own advisory.

Verify against the linked advisories before concluding, and cite the date you read each one:
- https://github.com/DMTF/libspdm/security/advisories/GHSA-7vfm-9mfh-j8p5
- https://github.com/DMTF/libspdm/pull/3902
- https://github.com/DMTF/libspdm/pull/3914
- https://github.com/DMTF/libspdm/commit/150bc5a7f9d1a04d86ba4f46c263b0ae7fe4a90f
- https://github.com/DMTF/libspdm/commit/97097d2c9c59f768afaa6198b6176d53a451f4bc
- https://github.com/DMTF/libspdm/releases/tag/3.8.3
- https://github.com/DMTF/libspdm/releases/tag/4.0.0-rc2
Do not conclude an asset is unaffected unless you checked it and the evidence covers both its version and the conditions above. If you could not check something, mark it unknown and say what is missing.

Report a table with one row per asset and these columns: Asset | Version or build | Status (affected, fixed, not applicable, unknown) | Compensating controls | Exposure (internet-facing, internal, none) | Evidence | Next action.

Entry: https://cve.now/CVE-2026-129306
For follow-up questions, use the cve.now MCP server at https://mcp.cve.now/mcp (no authentication), for example execute with name cve.get and arguments {"id": "CVE-2026-129306"}.

Timeline

  1. CVE published
  2. First seen by cve.now
  3. CISA SSVC assessment

    Exploitation: none · Automatable: no · Technical impact: partial

  4. Record last updated

Affected versions

  • DMTF libspdm

    fixed in 3.8.3; From 4.0.0-rc1 · fixed in 4.0.0-rc2

Evidence 9

Vendor advisory · 1

Establishes: Affected and fixed versions.

  1. Advisory

CVE record · 2

Establishes: The identifier and description.

  1. Record
  2. Record

Other links · 6

  1. Repository
  2. Repository
  3. Repository
  4. Repository
  5. Repository
  6. Repository

Corrections

None so far.

Something wrong on this page? Report an error. Every fix is listed here.

Questions about CVE-2026-129306

Is CVE-2026-129306 being exploited?

It is not in CISA's Known Exploited Vulnerabilities catalog, and CISA's SSVC assessment does not mark exploitation as active. That does not mean it has not been attacked: vendors and researchers can report attacks before CISA lists them. No public exploit code is tracked.Source: cve.now feed data

Which versions are affected by CVE-2026-129306?

libspdm: before 3.8.3; from 4.0.0-rc1 before 4.0.0-rc2.Source: cve.now feed data

How do I fix CVE-2026-129306?

Upgrade to a fixed version: 3.8.3, 4.0.0-rc2.Source: cve.now feed data