Quick answers
- Is CVE-2026-42067 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-42067 being exploited in the wild.
- How severe is CVE-2026-42067?
- 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 software before 0.2.0.
- Is there a fix for CVE-2026-42067?
- 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-42067 attacked?
- It is attacked with local access, in a hosted service.
- Am I affected by CVE-2026-42067?
- Check whether you run tdx_workload_attestation (crates.io) or Intel TDX Workload Attestation software 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
An improper certificate validation vulnerability in Intel TDX Workload Attestation's Ring 3 user applications allows integrity compromise via local access. An unauthenticated attacker with low complexity attack requirements can manipulate data; the CVSS vector indicates attack potential requiring specific system conditions (CVSS:4.0/AV:L/AC:L/AT:P/PR:N/UI:N/VC:N/VI:H/VA:N/SC:N/SI:N/SA:N). A patch is available in version 0.2.0.
Affected products
- Intel TDX Workload Attestation software before 0.2.0
Identifiers
- CVE-2026-42067
- GHSA-w4mf-755j-wjwc
- RUSTSEC-2026-0481
Timeline
- 2026-11-10: disclosed