CVE-2026-108268: enclave-os-virtual: RA-TLS challenge certificates were not bound to the TLS session
Enclave OS Virtual runs container workloads inside confidential virtual machines with end-to-end attestation. Prior to tdx-v0.2.43 and tdx-gpu-v0.6.27, the TDX/GPU RA-TLS certificate issuer placed the certificate public-key hash and client nonce in quote ReportData but omitted a value bound to the active TLS session. An attacker who obtained an enclave TLS private key could relay a genuine quote onto another connection, causing a relying party to accept an attacker-terminated connection as the attested enclave. This issue is fixed in tdx-v0.2.43 and tdx-gpu-v0.6.27.
Affected Software
Remediation
Recommended actions to resolve this vulnerability, in priority order.
- Upgrade
Upgrade
tdxto a version that resolves this vulnerability.Fixed in v0.2.43 - Upgrade
Upgrade
tdx-gputo a version that resolves this vulnerability.Fixed in v0.6.27
Event History
Frequently Asked Questions
What must an attacker obtain to exploit this issue?
The attacker must obtain an enclave TLS private key. With that key, they can relay a genuine attestation quote to a different connection and impersonate the attested enclave to a relying party.
Which deployments are affected?
Enclave OS Virtual TDX releases before tdx-v0.2.43 and Enclave OS Virtual TDX GPU releases before tdx-gpu-v0.6.27 are affected.
What should be upgraded to remediate the issue?
Upgrade Enclave OS Virtual TDX to tdx-v0.2.43 or later, or Enclave OS Virtual TDX GPU to tdx-gpu-v0.6.27 or later.