Description
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.
References
- www.cve.org/CVERecord ↗
- nvd.nist.gov/vuln/detail/CVE-2026-108268 ↗
- github.com/Privasys/enclave-os-virtual/commit/9a6be91e29f2b6738d0b77c33cd1ad5cd3d8a347 ↗
- github.com/Privasys/enclave-os-virtual/releases/tag/tdx-gpu-v0.6.27 ↗
- github.com/Privasys/enclave-os-virtual/releases/tag/tdx-v0.2.43 ↗
- github.com/Privasys/enclave-os-virtual/security/advisories/GHSA-p5fp-g94g-g9m9 ↗
- privasys.org/blog/binding-attestation-to-the-tls-session ↗
Related CVEs
← CVE Index: search every CVE from the last 30 days
This product uses the NVD API but is not endorsed or certified by the NVD. CVSS scores do not establish exploitation.