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.
- 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
- Fix
- None listed
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
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.
Upgrade to the fixed version, and do not rely on a single control for protection. More about Security feature bypass.
Is CVE-2026-129306 being exploited?
There is no known exploitation of CVE-2026-129306 in the wild and no public exploit code.
Sources
Also known as GHSA-7vfm-9mfh-j8p5, UBUNTU-CVE-2026-129306.