Vulnerability · CVE-2026-40693
Panic on a GCP launch endorsement without TDX measurements
Published Nov 10, 2026 · catalog updated Nov 11, 2026 · RustSec Rust
Last checked Nov 12, 2026. A connected source was read within the last 7 days.
Check if you run it
No confirmed exploitation is on record for CVE-2026-40693. EPSS is 0.10%. Act only if a listed version of RustSec Rust is installed.
Gaps on this record
- No vendor fix or required action is stored. Compare the linked advisory before you change production.
Same product and reporting
- RUSTSEC-2026-0501 · Unknown
- RUSTSEC-2026-0497 · Unknown
- RUSTSEC-2026-0499 · Unknown
- CVE-2026-42067 · Unknown
- RUSTSEC-2026-0500 · High
- Severity
- Unknown—
- Known exploitation
- Not in CISA/VulnCheck KEV
- EPSS
- 0.10%
- Remediation
- Advisory link
- Affected products
- crates.io tdx_workload_attestation
, available with the feature, read without checking that the golden measurement contains a TDX measurement. If a launch endorsement's golden measurement had no TDX measurements, the call panicked with an index out of bounds instead of returning an error. The panic is reached only after the endorsement's signing certificate and signature have been verified. Triggering it therefore requires a correctly signed endorsement that lacks TDX measurements. Intel describes the issue as improper input validation and classifies it as denial of service, with a CVSS 4.0 base score of 5.7, in INTEL-SA-01520. The flaw was corrected in [#87](https://github.com/IntelLabs/tdx-workload-attestation/pull/87), released in 0.2.0. The function now returns when the TDX measurement structure is missing or empty. Reported by [Borys Tsyrulnikov](https://borystsyrulnikov.dev).
Are you affected?
Enter the version you run. The result uses only the ranges stored on this record.
The check returns affected, not affected, or incomplete. It does not guess a version that is missing from the record.
- crates.io tdx_workload_attestation0.0.0-0 → 0.2.0
How to fix CVE-2026-40693
Upgrade
CVE-2026-40693 lists a fix boundary at 0.2.0. Compare the installed build with that boundary before you change production.
Version check
Seen in 0.0.0-0 → 0.2.0
Advisory
Open the cve_org record and follow its fix.
Official advisories
What to do
Three questions, each answered from this record only. Confirm the vendor advisory before you patch.
Should you patch?
No confirmed exploitation is on record for CVE-2026-40693. EPSS is 0.10%. Act only if a listed version of RustSec Rust is installed.
Which versions are affected?
Compare what you have installed with 0.0.0-0 → 0.2.0. Compare the installed version with the linked vendor advisory before you change production.
What should an analyst verify?
No weakness class is stored. EPSS 0.10%. There is no CISA KEV listing. No Exploit-DB or Metasploit reference is linked. Use the source links for the original advisory.
Code
The project this record applies to. Exploit listings stay in References.
Timeline
Detection, updates, and resolution for this record.
Nov 10, 2026 · GitHub Advisory Database
Detected
, available with the feature, read without checking that the golden measurement contains a TDX measurement. If a launch endorsement's golden measurement had no TDX measurements, the call panicked with an index out of bounds instead of returning an error. The panic is reached only after the endorsement's signing certificate and signature have been verified. Triggering it therefore requires a correc
Nov 11, 2026 · GitHub Advisory Database
Fix available
tdx_workload_attestation fixed in 0.2.0
Nov 11, 2026 · GitHub Advisory Database
Fix available
tdx_workload_attestation fixed in 0.2.0
Nov 11, 2026 · GitHub Advisory Database
Updated
, available with the feature, read without checking that the golden measurement contains a TDX measurement. If a launch endorsement's golden measurement had no TDX measurements, the call panicked with an index out of bounds instead of returning an error. The panic is reached only after the endorsement's signing certificate and signature have been verified. Triggering it therefore requires a correc
Sources
- CVE.orgVulnerability recordCVE-2026-40693
Official CVE identifier
cve.org - FIRST EPSSExploitation probabilityCVE-2026-40693
30-day exploitation probability 0.10%
first.org - GitHub Advisory DatabasePackage advisoryGHSA-gwf2-8595-qw97
GitHub Advisory Database record mirrored by OSV.
github.com - OpenSSF OSV / OSV ScannerPackage advisoryRUSTSEC-2026-0480
Panic on a GCP launch endorsement without TDX measurements
osv.dev - RustSec Advisory DBVendor advisoryCVE-2026-40693
, available with the feature, read without checking that the golden measurement contains a TDX measurement. If a launch endorsement's golden measurement had no TDX measurements, the call panicked with an index out of bounds instead of returning an error. The panic is reached only
crates.io
References
Freshness
Last verified in this catalog Nov 11, 2026. Significant claims (KEV, EPSS, CVSS, affected ranges) come from the source rows above — open the original publisher for the authoritative advisory.
- RustSec Advisory DBNov 12, 2026
- CVE.orgNov 11, 2026
- FIRST EPSSNov 11, 2026
- GitHub Advisory DatabaseNov 11, 2026
- OpenSSF OSV / OSV ScannerNov 11, 2026