# CVE-2026-129306: libspdm: libspdm_x509_verify_cert_chain() does not verify CA nameConstraints / pathLenConstraint

> Attackers with a subordinate certificate from a constrained CA can pass libspdm SPDM identity validation when only identity impersonation is allowed.

- **Severity:** Medium 4.4 (`CVSS:3.1/AV:N/AC:H/PR:H/UI:N/S:C/C:L/I:L/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** An administrator
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Harmful if only installed:** No
- **Needs a specific call:** Yes (`libspdm_x509_verify_cert_chain()`)
- **Fix available:** No
- **Published:** 16 Nov 2026
- **Updated:** 16 Nov 2026
- **Also known as:** GHSA-7vfm-9mfh-j8p5, UBUNTU-CVE-2026-129306

## What is CVE-2026-129306?

CVE-2026-129306 is a medium-severity security feature bypass vulnerability in DMTF libspdm, published on 16 Nov 2026. An attacker needs administrator access to exploit it, with no action from the victim.

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

Weakness: CWE-295 (Improper Certificate Validation)

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

An affected version is only exploitable if your software calls libspdm_x509_verify_cert_chain(). Many projects that include it are not exposed.


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

No fix has been published for CVE-2026-129306 yet. Limit exposure of the affected software until one is available.

## Is CVE-2026-129306 being exploited?

There is no known exploitation of CVE-2026-129306 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-129306 and fix it if it is affected.

What it is: CVE-2026-129306 is a medium-severity security feature bypass vulnerability in DMTF libspdm, published on 16 Nov 2026. An attacker needs administrator access to exploit it, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-129306 in the wild and no public exploit code.
Exposure: An affected version is only exploitable if your software calls libspdm_x509_verify_cert_chain(). Many projects that include it are not exposed.

Affected product: DMTF libspdm. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
   If an affected version is present, also search the code for calls to libspdm_x509_verify_cert_chain() and report whether any exist.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-129306/ (Markdown: https://insights.sbomify.com/CVE-2026-129306/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-129306
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-129306
- OSV: https://osv.dev/vulnerability/CVE-2026-129306

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-129306/
Summaries are generated and may contain mistakes; the official description above is the record.
