Is CVE-2026-40693 exploited in the wild?

No. Junglewise Threat Intelligence has no report of CVE-2026-40693 being exploited in the wild.

How severe is CVE-2026-40693?

Medium severity, with a CVSS score of 4, published 10 November 2026.

Which products and versions are affected?

tdx_workload_attestation (crates.io) SEMVER:introduced=0.0.0-0,fixed=0.2.0; Intel TDX Workload Attestation before 0.2.0.

Is there a fix for CVE-2026-40693?

Yes. tdx_workload_attestation (crates.io): upgrade to 0.2.0 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.

How is CVE-2026-40693 attacked?

It is attacked with local access, in a software library.

Am I affected by CVE-2026-40693?

Check whether you run tdx_workload_attestation (crates.io) or Intel TDX Workload Attestation at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

CVE-2026-40693: Intel TDX Workload Attestation Software input validation denial of service

CVE-2026-40693 · Severity: medium · CVSS 4 · Published 2026-11-10

Intel TDX Workload Attestation is a software component that validates trusted virtual workloads in Intel's Trusted Domain Extension environments. An authenticated attacker with local access can trigger a denial of service condition through improper input handling, causing the system to become unavailable.

Vendors: crates.io, Intel.

Quick answers

Is CVE-2026-40693 exploited in the wild?: No. Junglewise Threat Intelligence has no report of CVE-2026-40693 being exploited in the wild.
How severe is CVE-2026-40693?: Medium severity, with a CVSS score of 4, published 10 November 2026.
Which products and versions are affected?: tdx_workload_attestation (crates.io) SEMVER:introduced=0.0.0-0,fixed=0.2.0; Intel TDX Workload Attestation before 0.2.0.
Is there a fix for CVE-2026-40693?: Yes. tdx_workload_attestation (crates.io): upgrade to 0.2.0 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
How is CVE-2026-40693 attacked?: It is attacked with local access, in a software library.
Am I affected by CVE-2026-40693?: Check whether you run tdx_workload_attestation (crates.io) or Intel TDX Workload Attestation at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

How to fix

tdx_workload_attestation (crates.io): upgrade to 0.2.0 or later
```
cargo update -p tdx_workload_attestation
```

Technical details

Improper input validation in the Ring 3 user application component of Intel TDX Workload Attestation allows an authenticated local attacker to trigger a denial of service via a high-complexity attack without user interaction. The vulnerability affects the availability of the vulnerable system with no confidentiality or integrity impact.

Affected products

Intel TDX Workload Attestation before 0.2.0

Identifiers

CVE-2026-40693
GHSA-gwf2-8595-qw97
RUSTSEC-2026-0480

Timeline

2026-11-10: disclosed

References

https://intel.com/content/www/us/en/security-center/advisory/intel-sa-01520.html

This page as Markdown. Free to reuse under CC BY 4.0 with a link back.