CVE-2026-129306 json
libspdm: libspdm_x509_verify_cert_chain() does not verify CA nameConstraints / pathLenConstraint
published last mo. modified yesterday also EUVD-2026-126576 , GHSA-7vfm-9mfh-j8p5
Unreviewed: the maintainers' own advisory
Published by the maintainers on their GitHub repository DMTF/libspdm. GitHub has not reviewed it into the GitHub Advisory Database, so the affected packages and versions are the maintainers' word. Read the full advisory on GitHub.
- cvss
- 4.4
- version 3.1, CNA
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 0.2%
- EPSS 0.2% chance of exploitation in 30 days, percentile 5%
- public exploits
- 0
- none known
Summary
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.
Patch / fix
- github.com/DMTF/libspdm@150bc5a commit
- github.com/DMTF/libspdm@97097d2 commit
- github.com/DMTF/libspdm#3902 pull request
- github.com/DMTF/libspdm#3914 pull request
- github.com/DMTF/libspdm/releases/tag/3.8.3 release
- github.com/DMTF/libspdm/releases/tag/4.0.0-rc2 release
Is CVE-2026-129306 in your stack? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.
Check with FencerCISA SSVC
- Exploitation
- none
- Automatable
- no
- Technical impact
- partial
- Assessed
- yesterday
Exploit prediction
0.16% chance of exploitation in the next 30 days, higher than 5% of all scored CVEs (FIRST EPSS, 2026-11-18).
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| CNA | 3.1 | 4.4 | CVSS:3.1/AV:N/AC:H/PR:H/UI:N/S:C/C:L/I:L/A:N |
Affected products
- DMTF libspdm
Classification
- Weakness
-
- CWE-295 Improper Certificate Validation
References
- github.com /DMTF/libspdm/pull/3902
- github.com /DMTF/libspdm/pull/3914
- github.com /DMTF/libspdm/commit/150bc5a7f9d1a04d86ba4f46c263b0ae7fe4a90f
- github.com /DMTF/libspdm/commit/97097d2c9c59f768afaa6198b6176d53a451f4bc
-
github.com
/DMTF/libspdm/security/advisories/GHSA-7vfm-9mfh-j8p5
advisory
- github.com /DMTF/libspdm/releases/tag/3.8.3
- github.com /DMTF/libspdm/releases/tag/4.0.0-rc2
Sources
- CVE List CVE-2026-129306
- NVD CVE-2026-129306
- Maintainer advisory GHSA-7vfm-9mfh-j8p5
Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.
The maintainers of DMTF/libspdm published their own advisory on GitHub. Reviewed sources take precedence over it.