Quick answers
- Is CVE-2026-108268 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-108268 being exploited in the wild.
- How severe is CVE-2026-108268?
- Informational severity, published 9 October 2026.
- Which products and versions are affected?
- Privasys Enclave OS Virtual before tdx-v0.2.43 and tdx-gpu-v0.6.27.
- Is there a fix for CVE-2026-108268?
- Yes: fixed in tdx-v0.2.43, tdx-gpu-v0.6.27. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
- How is CVE-2026-108268 attacked?
- It is attacked over the network, in a network appliance.
- Am I affected by CVE-2026-108268?
- Check whether you run Privasys Enclave OS Virtual 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
- Fixed in: tdx-v0.2.43, tdx-gpu-v0.6.27
Technical details
A flaw in the RA-TLS (Remote Attestation TLS) certificate issuer's quote generation failed to bind the attestation quote to the active TLS session; the ReportData field contained only the certificate public-key hash and client nonce, omitting the TLS session channel binder. An attacker with an enclave's TLS private key could relay a genuine attestation quote to another connection, bypassing session binding verification. The fix adds channel-binding material to the quote's report_data field, causing replayed quotes to fail binder validation.
Affected products
- Privasys Enclave OS Virtual before tdx-v0.2.43 and tdx-gpu-v0.6.27
Timeline
- 2026-10-09: disclosed