Paper/Archive/CVE-2026-108268

CVE-2026-108268

Privasys enclave-os-virtual — enclave-os-virtual: RA-TLS challenge certificates were not bound to the TLS session

Description · from the CVE record

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

ProductAffectedFixed inSource
enclave-os-virtual< tdx-v0.2.43–CNA
enclave-os-virtual< tdx-gpu-v0.6.27–CNA

Scores by source

GitHub_M (CNA)9.1CVSS:4.0/AV:N/AC:H/AT:P/PR:N/UI:N/VC:H/VI:H/VA:N/SC:N/SI:N/SA:N
CISA ADPSSVCExploitation: none · Automatable: no · Technical impact: total

References

refgithub.com/Privasys/enclave-os-virtual/security/advisories/GHSA-p5fp-g94g-g9m9refgithub.com/Privasys/enclave-os-virtual/commit/9a6be91e29f2b6738d0b77c33cd1ad5cd3d8a347refgithub.com/Privasys/enclave-os-virtual/releases/tag/tdx-gpu-v0.6.27refgithub.com/Privasys/enclave-os-virtual/releases/tag/tdx-v0.2.43refprivasys.org/blog/binding-attestation-to-the-tls-session