CVE-2026-129306

MEDIUMPre-NVD 4.44.4
EchelonGraph scoreMEDIUM confidence

“—” beside the score: it is equal to the CVSS score beside it.

This medium-severity CVE scores 4.4 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit probability: 0.2% (5th percentile of EPSS-scored CVEs). No GitHub Security Advisory CVSS is on record for this CVE.

Triggered by: Headline CVSS from a secondary CVSS source
Sources: EPSS, a secondary CVSS source

Also known asEUVD-2026-126576 (ENISA EUVD)Source: ENISA EUVD

4.4EG
EchelonGraph verdictMonitorRemediate within your standard update timelines (the SSVC decision on this page).
  • Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS PROB: 0.2%CVSS: 4.4Exploit: None knownExposed services: Not assessed

A fix is available — apply it.

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 v3
4.4
EG Score
4.4MEDIUMmedium confidence
EG Risk
20
EG Risk 20/100

EG Risk is EchelonGraph's 0–100 priority score. It fuses impact severity (EG Severity, the CVSS base score, never the KEV-floored or EPSS-lifted EG Score) with real-world exploitation and automatability, under weights EchelonGraph set by hand, so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner.

How it’s computed (value × EchelonGraph’s weight)
Severity44% × 45%
Impact severity (EG Severity): CVSS 4.4 of 10. Never the KEV-floored or EPSS-lifted EG Score.
Exploitation0.2% × 40%
FIRST EPSS: the 30-day exploitation probability when EchelonGraph scored this CVE.
Automatability0% × 15%
CISA's SSVC Automatable value: no (Vulnrichment).
SSVC (CISA's decision table, applied by EchelonGraph): Track at every mission impact level.
Exploitation none (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE.
Action: A fix is available. Apply it within your standard update timelines.
EPSS PROB
0.2%
EPSS %ILE
5th
KEV
Not listed

What the EG score is made of (scorer v4.0: the three questions the 0–10 score mixes, published apart · methodology)

The EG score (4.4): severity, escalated by confirmed exploitation. This CVE's 4.4 is its impact severity (EG Severity), not escalated.

EG Severity
4.4 MEDIUMCVSS-B, impact only: no KEV listing, EPSS or EG-KEV tier raises it.a secondary CVSS source · CVSS v3.0 or v3.1
EG Likelihood
0.2% within 30 daysSource: FIRST EPSS (model v2026.06.15, score date 2026-11-19). FIRST's exploitation probability, not an EchelonGraph model.
Confirmed exploitation
None on record (CISA KEV, EG-KEV Tier 1)Reported apart from the likelihood: an observed fact, not a probability.
EG Priority
SSVC Track at medium mission impactTrack at every mission impact level.CISA BOD 26-04: 60 days if the affected system is publicly exposed; Fix on system upgrade if it is not.Each input and its source, and whom BOD 26-04 binds: the SSVC and BOD 26-04 blocks below.

SSVC (CISA's decision table, applied by EchelonGraph)Track at every mission impact level.

A fix is available. Apply it within your standard update timelines.

Exploitation none (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE. Mission impact is CISA's Mission & Well-being decision point, and only you can judge it. CISA's table makes it high when Mission Prevalence is Essential — the vulnerable component "directly provides capabilities that constitute at least one MEF for at least one entity" (MEF: mission essential function) — or when Public Well-Being Impact is Irreversible: "multiple fatalities are likely", the cyber-physical system "is likely lost or destroyed", "extreme or serious externalities" are imposed on other parties, or social systems such as elections or the financial grid "are destabilized and potentially collapse". CISA's decision table

BOD 26-04 (CISA's remediation timeline, Table 1)60 days if the affected system is publicly exposed; Fix on system upgrade if it is not.

The score's inputs: In CISA KEV no (CISA's KEV catalog) · Automatable no (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). Whether your system is publicly exposed is yours to answer. BOD 26-04 binds US Federal Civilian Executive Branch agencies; for anyone else it is CISA's published timeline, a reference rather than an obligation. The directive · how EchelonGraph applies it

Published

November 16, 2026

Last Modified

November 16, 2026

Advisory Details (7)

Auto-updated Nov 16, 2026
Patch available. Sources: github, github_commit, github_pr, github_release.
GitHub release Patch Available

4.0.0-rc2

Patch available: DMTF/libspdm 4.0.0-rc2 (pre-release)

https://github.com/DMTF/libspdm/releases/tag/4.0.0-rc2
GitHub release Patch Available

3.8.3

Patch available: DMTF/libspdm 3.8.3

https://github.com/DMTF/libspdm/releases/tag/3.8.3
GitHub commit Patch Available

commit 97097d2c9c59 (DMTF/libspdm)

Patch available: DMTF/libspdm 3.8.3 (contains commit 97097d2c9c59)

https://github.com/DMTF/libspdm/commit/97097d2c9c59f768afaa6198b6176d53a451f4bc
GitHub commit Patch Available

commit 150bc5a7f9d1 (DMTF/libspdm)

Patch available: DMTF/libspdm 4.0.0-rc2 (contains commit 150bc5a7f9d1)

https://github.com/DMTF/libspdm/commit/150bc5a7f9d1a04d86ba4f46c263b0ae7fe4a90f
GitHub pull request Patch Available

Cert validation 3.8 branch

Patch available: DMTF/libspdm 3.8.3 (PR #3914 merged 2026-09-28)

https://github.com/DMTF/libspdm/pull/3914
GitHub pull request Patch Available

Cert validation

Patch available: DMTF/libspdm 4.0.0-rc2 (PR #3902 merged 2026-09-22)

https://github.com/DMTF/libspdm/pull/3902
GitHub advisoryMentions a patch (unverified)

DMTF-2026-0004: libspdm_x509_verify_cert_chain() does not verify CA nameConstraints / pathLenConstraint · Advisory · DMTF/libspdm · GitHub

https://github.com/DMTF/libspdm/security/advisories/GHSA-7vfm-9mfh-j8p5

Weakness Classification(1)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Data Freshness Timeline

(refreshed 7× in last 7d / 7× in last 30d)

Each row is a time one of our pipelines fetched, updated or re-scored this CVE. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed its CVE.org record (CNA or CISA ADP). An arrow marks a change the record states ("CVSS v3 → 9.1"); EPSS and GHSA rows show the values recorded at that time, not what changed (EPSS values are rounded; hover one for the exact figures). "EchelonGraph re-scored" is our own recompute of this CVE's score, not an update from a source, and is not counted in the refreshes above. Most recent first.

  1. 2026-11-21 16:38 UTCEPSS rescoreEPSS 0.2% · 5th percentile
  2. 2026-11-20 16:36 UTCEPSS rescoreEPSS 0.2% · 5th percentile
  3. 2026-11-20 05:42 UTCEchelonGraph re-scored
  4. 2026-11-19 16:33 UTCEPSS rescoreEPSS 0.2% · 5th percentile
  5. 2026-11-18 16:34 UTCEPSS rescoreEPSS 0.2% · 5th percentile
  6. 2026-11-17 16:34 UTCEPSS rescoreEPSS 0.2% · 5th percentile
  7. 2026-11-16 19:03 UTCENISA EUVD ID recordedEUVD-2026-126576 · Source: ENISA EUVD
  8. 2026-11-16 18:29 UTCEchelonGraph re-scored
  9. 2026-11-16 18:06 UTCEchelonGraph re-scoredFirst assessed: 4.4 MEDIUM
  10. 2026-11-16 18:03 UTCMITRE cvelistV5first tracked

Frequently asked(5)

What is CVE-2026-129306?
CVE-2026-129306 is a medium-severity vulnerability; its CVE record was published on November 16, 2026. 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…
When was the CVE record for CVE-2026-129306 published?
The CVE record for CVE-2026-129306 was published on November 16, 2026. That is the record's publication date; the vulnerability itself may have been made public earlier. EchelonGraph's copy of the record carries a last-modified date of November 16, 2026; the record at its source may have been updated since.
Is CVE-2026-129306 actively exploited?
CVE-2026-129306 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.2% probability of exploitation in the next 30 days (5th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-129306?
CVE-2026-129306 has a CVSS base score of 4.4 (a secondary CVSS source that NVD displays; NVD's own analysis pending).
How do I remediate CVE-2026-129306?
A fix for CVE-2026-129306 is available: update to the fixed version the vendor names in its advisory.

Dependency Blast Radius

Explore the affected products and dependency analysis for CVE-2026-129306

Explore →

Is Your Infrastructure Affected by CVE-2026-129306?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.