Skip to main content
VulnerabilityPublished

CVE-2026-40693: Tdx workload attestation · Panic on a GCP launch endorsement without TDX measurements

Affects tdx_workload_attestationSource GCVE Database

0
Compare
Authoritative record:CVE-2026-40693· Medium 5.7

Not known to be exploited · CVSS 5.7 Medium : upgrade to 0.2.0 when convenient.

Data as of 11 Nov 2026, 10:33 UTC

CVSS 4.0 base score
5.7Medium
How severe the flaw is on the 0–10 CVSS scale.

Thin evidence

One scorer or none
CVSS scores by source
CNA (intel)CVSS 4.05.7
CNACVSS 4.05.7
Patch
Available – fixed in 0.2.0
CVSS:4.0/AV:L/AC:H/AT:P/PR:L/UI:N/VC:N/VI:N/VA:H/SC:N/SI:N/SA:N

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 10 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 10 Nov 2026.

What to do

Upgrade tdx_workload_attestation to 0.2.0.

Affected software

ProductAffectedFixed in
crates.iotdx_workload_attestationpkg:cargo/tdx_workload_attestationOther threatsAffected
  • >=0.0.0-0 <0.2.0
Fixed in
  • 0.2.0

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

AI-suggested

Upgrade the tdx_workload_attestation crate to version 0.2.0 or later, where the issue is fixed. The patched version returns an error instead of panicking when TDX measurements are missing, preventing denial of service.

Description

A vulnerability in the tdx_workload_attestation Rust crate allows a panic (denial of service) when processing a GCP launch endorsement that lacks TDX measurements. The issue occurs because the code reads a TDX measurement without verifying its presence, causing an index out of bounds panic. This flaw is fixed in version 0.2.0 by returning an error instead of panicking.

References

Community reviews

Loading reviews…