CVE-2026-129306

libspdm: libspdm_x509_verify_cert_chain() does not verify CA nameConstraints / pathLenConstraint

Published Nov 16, 2026 CVSS 3.1 · 4.4 Medium EPSS n/a KEV · Not listed
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.

Analysis

AI-generated

Technical impact

libspdm_x509_verify_cert_chain() validates certificate signatures incrementally instead of verifying the entire X.509 path, meaning the CA nameConstraints and pathLenConstraint are not enforced. This flaw allows an attacker who possesses a subordinate issuer certificate that exceeds the CA constraints to present a certificate that is accepted as a valid SPDM identity, effectively enabling identity impersonation. The weakness is classified under CWE-295: Improper Certificate Validation, and can impact the confidentiality and integrity of SPDM authentication in systems relying on libspdm for identity verification.

Affected Systems

DMTF:libspdm is affected, with the issue present in all releases prior to 3.8.3 and prior to 4.0.0‑rc2. Applications using libspdm versions 3.8.2 or earlier, or 4.0.0‑rc1 or earlier, are vulnerable until the corresponding security fix is applied.

Risk and Exploitability

The CVSS score of 4.4 indicates a low‑to‑medium severity, and no EPSS score is available, suggesting a low probability of active exploitation. The vulnerability is not listed in the CISA KEV catalog. Exploitation requires a deployment that uses libspdm’s backend validation without supplementary chain validation mechanisms, relies on a pinned root that cannot be substituted, and has a measurement policy that permits identity impersonation alone to satisfy acceptance. In such constrained scenarios, an attacker could bypass pathLenConstraint or nameConstraints restrictions by presenting a subordinate certificate, but broad applicability is limited because many deployments include additional validation or policy checks. The mbedTLS backend also lacks nameConstraints enforcement, which further constrains the real‑world risk.

Remediation

No solution or workaround provided in the CVE record.

OpenCVE Recommended Actions

  • Upgrade libspdm to version 3.8.3 or later, or to 4.0.0‑rc2 or later, to enable full‑chain certificate path validation.
  • Ensure that the application performs additional certificate‑chain validation beyond libspdm to defend against constraints bypass.
  • If using the mbedTLS backend, verify that nameConstraints enforcement is available or switch to a backend that implements it; alternatively, prevent reliance on mbedTLS for critical identity validation.
  • Review and tighten the deployment’s measurement policy so that identity impersonation alone cannot satisfy acceptance requirements.
  • Monitor deployments for anomalies related to SPDM identity verification and apply any new vendor advisories promptly.

Generated by OpenCVE AI on November 16, 2026 at 19:35 UTC.

Tracking

Sign in to view the affected projects.

Advisories

No advisories available
History
Type Values Removed Values Added
Metrics ssvc

{'options': {'Automatable': 'no', 'Exploitation': 'none', 'Technical Impact': 'partial'}, 'version': '2.0.3'}

Type Values Removed Values Added
First Time appeared Dmtf
Dmtf libspdm
Vendors & Products Dmtf
Dmtf libspdm
Type Values Removed Values Added
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.
Title libspdm: libspdm_x509_verify_cert_chain() does not verify CA nameConstraints / pathLenConstraint
Weaknesses CWE-295
References
Metrics cvssV3_1

{'score': 4.4, 'vector': 'CVSS:3.1/AV:N/AC:H/PR:H/UI:N/S:C/C:L/I:L/A:N'}

Weaknesses
  • CWE-295

    Improper Certificate Validation

Sources

Status
PUBLISHED
Assigner
GitHub_M
Published
Updated
Nov 16, 2026, 6:56 PM
Reserved
Nov 13, 2026, 10:30 PM
Status
Received
Published
Nov 16, 2026, 6:17 PM
Modified
Nov 16, 2026, 7:17 PM