{"dataType":"CVE_RECORD","dataVersion":"5.2","cveMetadata":{"cveId":"CVE-2026-108268","assignerOrgId":"a0819718-46f1-4df5-94e2-005712e83aaa","state":"PUBLISHED","assignerShortName":"GitHub_M","dateReserved":"2026-10-09T17:33:15.410Z","datePublished":"2026-10-09T21:13:33.595Z","dateUpdated":"2026-10-09T21:13:33.595Z"},"containers":{"cna":{"title":"enclave-os-virtual: RA-TLS challenge certificates were not bound to the TLS session","problemTypes":[{"descriptions":[{"cweId":"CWE-346","lang":"en","description":"CWE-346: Origin Validation Error","type":"CWE"}]}],"metrics":[{"cvssV4_0":{"attackVector":"NETWORK","attackComplexity":"HIGH","attackRequirements":"PRESENT","privilegesRequired":"NONE","userInteraction":"NONE","vulnConfidentialityImpact":"HIGH","vulnIntegrityImpact":"HIGH","vulnAvailabilityImpact":"NONE","subConfidentialityImpact":"NONE","subIntegrityImpact":"NONE","subAvailabilityImpact":"NONE","baseScore":9.1,"baseSeverity":"CRITICAL","vectorString":"CVSS:4.0/AV:N/AC:H/AT:P/PR:N/UI:N/VC:H/VI:H/VA:N/SC:N/SI:N/SA:N","version":"4.0"}}],"references":[{"name":"https://github.com/Privasys/enclave-os-virtual/security/advisories/GHSA-p5fp-g94g-g9m9","tags":["x_refsource_CONFIRM"],"url":"https://github.com/Privasys/enclave-os-virtual/security/advisories/GHSA-p5fp-g94g-g9m9"},{"name":"https://github.com/Privasys/enclave-os-virtual/commit/9a6be91e29f2b6738d0b77c33cd1ad5cd3d8a347","tags":["x_refsource_MISC"],"url":"https://github.com/Privasys/enclave-os-virtual/commit/9a6be91e29f2b6738d0b77c33cd1ad5cd3d8a347"},{"name":"https://github.com/Privasys/enclave-os-virtual/releases/tag/tdx-gpu-v0.6.27","tags":["x_refsource_MISC"],"url":"https://github.com/Privasys/enclave-os-virtual/releases/tag/tdx-gpu-v0.6.27"},{"name":"https://github.com/Privasys/enclave-os-virtual/releases/tag/tdx-v0.2.43","tags":["x_refsource_MISC"],"url":"https://github.com/Privasys/enclave-os-virtual/releases/tag/tdx-v0.2.43"},{"name":"https://privasys.org/blog/binding-attestation-to-the-tls-session","tags":["x_refsource_MISC"],"url":"https://privasys.org/blog/binding-attestation-to-the-tls-session"}],"affected":[{"vendor":"Privasys","product":"enclave-os-virtual","versions":[{"version":"< tdx-v0.2.43","status":"affected"},{"version":"< tdx-gpu-v0.6.27","status":"affected"}]}],"providerMetadata":{"orgId":"a0819718-46f1-4df5-94e2-005712e83aaa","shortName":"GitHub_M","dateUpdated":"2026-10-09T21:13:33.595Z"},"descriptions":[{"lang":"en","value":"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."}],"source":{"advisory":"GHSA-p5fp-g94g-g9m9","discovery":"UNKNOWN"}}}}