CVE-2026-129306
Received Received - Intake

X.509 Path Validation Bypass in libspdm

Vulnerability report for CVE-2026-129306, including description, CVSS score, EPSS score, affected products, exploitability, helpful resources, and attack-flow context.

Publication date: 2026-11-16

Last updated on: 2026-11-16

Assigner: GitHub, Inc.

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.

CVSS Scores

EPSS Scores

Probability:
Percentile:

Meta Information

Published
2026-11-16
Last Modified
2026-11-16
Generated
2026-11-16
AI Q&A
2026-11-16
EPSS Evaluated
N/A
NVD
EUVD

Affected Vendors & Products

Currently, no data is known.

Helpful Resources

Exploitability

CWE
CWE Icon
KEV
KEV Icon
CWE ID Description
CWE-295 The product does not validate, or incorrectly validates, a certificate.

Attack-Flow Graph

AI Quick Actions

Instant insights powered by AI
Executive Summary

CVE-2026-129306 is a vulnerability in libspdm, a library implementing DMTF SPDM specifications. It involves improper X.509 certificate chain validation where the function libspdm_x509_verify_cert_chain() checks signatures link-by-link instead of validating the full chain. This allows attackers with valid issuer credentials in a multi-tier PKI to present subordinate certificates exceeding pathLenConstraint or nameConstraints, potentially bypassing constraints if the application relies solely on libspdm's backend validation without additional chain validation.

Detection Guidance

Detecting this vulnerability requires checking if your libspdm version is below 3.8.3 or 4.0.0-rc2. Use commands like 'libspdm version' or inspect package metadata to verify the installed version. If using OpenSSL or mbedTLS backend, ensure full-chain validation is enabled in SPDM implementations.

Impact Analysis

This vulnerability may allow an attacker to impersonate a legitimate entity in SPDM identity validation if specific conditions are met: the application uses libspdm's backend validation without extra chain validation, the pinned root cannot be substituted, and the deployment's measurement policy accepts identity impersonation alone. Exploitation requires the attacker to hold a valid issuer credential below a constrained CA.

Mitigation Strategies
  • Upgrade libspdm to version 3.8.3 or 4.0.0-rc2 or later to address the certificate chain validation flaw.
  • If using mbedTLS, note that nameConstraints enforcement is not supported; consider switching to OpenSSL backend if possible.
  • Review SPDM deployments to ensure additional certificate-chain validation mechanisms are in place beyond libspdm's backend.

Chat Assistant

Ask questions about this CVE
Hi! I’m here to help you understand CVE-2026-129306. Ask me anything about the vulnerability, its impact, or mitigation strategies.
0/70

EPSS Chart

Security Radar

News mentioning this vulnerability
Loading related security news...