Skip to main content
CVE-2026-129306VulnerabilityPublished Updated

Edk2: Prior to 3.8.3 and 4.0.0-rc2, libspdm_x509_verify_cert_chain() in os_stub/cryptlib_openssl/pk/x509.c and

Affects edk2Source GCVE Database

0
Compare
Authoritative record:CVE-2026-129306· Medium 4.4

Not known to be exploited · CVSS 4.4 Medium · fixed in 3.8.3 : update edk2 when convenient.

Data as of 18 Nov 2026, 15:50 UTC

CVSS 3.1 base score
4.4Medium
How severe the flaw is on the 0–10 CVSS scale.

Thin evidence

One scorer or none
CVSS scores by source
CNA (GitHub_M)CVSS 3.14.4
Patch
Available – fixed in 3.8.3
CVSS:3.1/AV:N/AC:H/PR:H/UI:N/S:C/C:L/I:L/A:N

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 16 Nov 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponized: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 17 Nov 2026.

What to do

Affected software

ProductAffectedFixed in
Ubuntu 26.10edk2pkg:deb/ubuntu/edk2?arch=source&distro=stonkingOther threatsAffected
  • 2025.11-3ubuntu7 – 2026.05-2ubuntu3
5 affected builds
Fixed in–
Ubuntu 26.10edk2-hwepkg:deb/ubuntu/edk2-hwe?arch=source&distro=stonkingOther threatsAffected
  • 2025.11-3ubuntu8 – 2026.05-2ubuntu3
5 affected builds
Fixed in–
Ubuntu 26.04 LTSedk2pkg:deb/ubuntu/edk2?arch=source&distro=resoluteOther threatsAffected
  • 2025.02-8ubuntu3 – 2025.11-3ubuntu7.3
5 affected builds
Fixed in–
Ubuntu 26.04 LTSedk2-hwepkg:deb/ubuntu/edk2-hwe?arch=source&distro=resoluteOther threatsAffected
  • =2025.11-3ubuntu6
  • =2025.11-3ubuntu8
  • =2025.11-3ubuntu8.2
Fixed in–
Ubuntu 24.04 LTSedk2pkg:deb/ubuntu/edk2?arch=source&distro=nobleOther threatsAffected
  • 2023.05-2 – 2024.02-2ubuntu0.10
18 affected builds
Fixed in–
Ubuntu 22.04 LTSedk2pkg:deb/ubuntu/edk2?arch=source&distro=jammyOther threatsAffected
  • 2021.08-3 – 2022.02~rc1-1ubuntu1
17 affected builds
Fixed in–

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

AI-suggested

Upgrade libspdm to version 3.8.3 or later, or 4.0.0-rc2 or later, where full-chain certificate validation is implemented. Deployments using the mbedTLS backend should be aware that nameConstraints enforcement remains unimplemented upstream. Additional certificate chain validation mechanisms beyond libspdm's backend validation can mitigate this issue. No other specific mitigations are indicated.

Description

A vulnerability in libspdm prior to versions 3.8.3 and 4.0.0-rc2 allows improper certificate chain validation. The function libspdm_x509_verify_cert_chain() validates certificates one link at a time instead of the entire X.509 path. This can enable an attacker with a valid subordinate issuer credential to present a certificate that violates pathLenConstraint or nameConstraints and be accepted for SPDM identity validation under specific deployment conditions. The mbedTLS backend remains unable to enforce nameConstraints due to upstream limitations. The issue is fixed in libspdm versions 3.8.3 and 4.0.0-rc2.

References

Community reviews

Loading reviews…