CVE-2026-129306 · Package
NO FIX YET · SEE WHAT TO DO
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.
first public Sep 29, 2026 · 1 source
Check it with your coding agent
It reads this page and tells you if your code or app is affected.
Applications that use libspdm's built-in backend certificate validation with a pinned root and a constrained multi-tier PKI, where the measurement policy accepts identity alone. Systems that add their own full-chain certificate validation, or that substitute the pinned root, are not exposed. The mbedTLS backend cannot enforce nameConstraints regardless of version.
Not affected if custom-chain-validation, measurement-policy-requires-more, pinned-root-not-used
Who cares device-attestation, embedded, firmware, libspdm, spdm
3.8.3 and 4.0.0-rc2 contain the fix; earlier versions are affected.libspdm_x509_verify_cert_chain() and confirm whether your application adds its own certificate-chain validation.3.8.3 or 4.0.0-rc2, which validate the complete certificate path.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.
Are you affected?
Ask from here. InfraStack checks the affected versions against your stack and answers in your inbox.
InfraStack checks the affected versions against your stack and answers in Slack, with the evidence and the fix.
InfraStack checks it against your stack and answers on your report, with the evidence and the fix.
NVD data is provided by NIST and is public domain. Posts quoted belong to their authors.