---
id: "CVE-2026-129306"
page: "https://infrastack.ai/live/CVE-2026-129306"
kind: "vulnerability"
aliases: ["CVE-2026-129306"]
title: "libspdm: certificate chains checked one link at a time, allowing impersonation"
severity: "medium"
cvss: 4.4
epss: null
exploited: false
status: "open"
category: "package"
products: []
ecosystems: []
tags: ["device-attestation", "embedded", "firmware", "libspdm", "package", "spdm"]
not_affected_if: ["custom-chain-validation", "measurement-policy-requires-more", "pinned-root-not-used"]
published_at: "2026-11-16T18:17:31+00:00"
first_seen_at: "2026-11-16T18:38:03+00:00"
updated_at: "2026-11-16T18:39:12+00:00"
sources: [{"source": "nvd", "url": "https://nvd.nist.gov/vuln/detail/CVE-2026-129306", "first_seen_at": "2026-11-16T18:38:03+00:00"}]
exploit_sources: []
---

# libspdm: certificate chains checked one link at a time, allowing impersonation

Link for people: https://infrastack.ai/live/CVE-2026-129306 (this .md is for agents)

libspdm, a sample implementation of the DMTF SPDM device-attestation protocol, validates X.509 certificate chains one link at a time instead of the full path. A holder of a valid credential below a constrained CA can present a subordinate certificate that breaks path or name constraints and may be accepted as a device identity.

_Summary, check and fix written by a model from the sources; labelled as such._

## How to check

- Check the libspdm version in your build: `3.8.3` and `4.0.0-rc2` contain the fix; earlier versions are affected.
- Look for calls to `libspdm_x509_verify_cert_chain()` and confirm whether your application adds its own certificate-chain validation.
- Check whether you use the mbedTLS backend, which cannot enforce nameConstraints.

## Fix

- libspdm: upgrade to `3.8.3` or `4.0.0-rc2`, which validate the complete certificate path.

## Timeline

- 2026-11-16T18:38:03+00:00 nvd https://nvd.nist.gov/vuln/detail/CVE-2026-129306

## Documents

- [advisory] Vendor advisory: github.com https://github.com/DMTF/libspdm/security/advisories/GHSA-7vfm-9mfh-j8p5
- [fix] Patch: github.com https://github.com/DMTF/libspdm/commit/150bc5a7f9d1a04d86ba4f46c263b0ae7fe4a90f
- [fix] Patch: github.com https://github.com/DMTF/libspdm/commit/97097d2c9c59f768afaa6198b6176d53a451f4bc
- [fix] Release notes: github.com https://github.com/DMTF/libspdm/releases/tag/3.8.3
- [fix] Release notes: github.com https://github.com/DMTF/libspdm/releases/tag/4.0.0-rc2

## From the sources

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.

---

_Free to read, with fair use of about 60 pages a minute. For higher limits or API access: sales@infrastack.ai_
