Track vulnerabilities like this one. Sign up free to get alerted when software you use is affected.
8.6

Enclave OS Virtual may accept forged attestation connections

CVE-2026-108268 · published 1 day ago
Summary

The Enclave OS Virtual software that runs container workloads in secure virtual machines could be tricked into accepting a fake proof of its identity if an attacker steals its TLS private key. This happens because the certificate used for remote attestation was not linked to the active TLS session, allowing a replay of a real attestation on a different connection. Updating to the latest versions (tdx‑v0.2.43 or tdx‑gpu‑v0.6.27) resolves the issue; apply those updates as soon as possible.

What to do

The CVE record does not list a fixed version. Check the vendor's site or the advisory links below - a fix may already be released.

Affected software
VendorProductAffected versions
privasys enclave-os-virtual < tdx-v0.2.43
Original advisory text
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.
References
Severity
8.6 High
Exploitation
<1% chance of attack within 30 days
Type
CWE-346Origin Validation Error
Timeline
Published9 Oct 2026
Updated11 Oct 2026
First seen9 Oct 2026
Sources
CVE-2026-108268 · NVD
CVE-2026-108268 · MITRE
CVE-2026-108268 · OSV
GHSA-p5fp-g94g-g9m9 · GHSA
Track software like this
Free during beta