CVE-2026-108268

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

Published Oct 9, 2026 CVSS 4.0 · 9.1 Critical EPSS < 1% KEV · Not listed
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.

Analysis

AI-generated

Technical impact

Enclave OS Virtual previously omitted a value bound to the active TLS session in the RA‑TLS certificate issuer’s quote ReportData, allowing an attacker who possessed the enclave TLS private key to relay a genuine quote onto a different connection. This flaw lets a relying party accept a maliciously terminated connection as if it were from the authenticated enclave, effectively spoofing attestation and bypassing security checks on the connection. The weakness is a classic instance of Untrusted Data (CWE‑346).

Affected Systems

Privasys Enclave OS Virtual is affected. Versions prior to tdx-v0.2.43 and tdx-gpu-v0.6.27 lack the mitigation that binds the TLS session to the attestation data; these versions should be considered vulnerable. Newer releases that include these fixes do not exhibit this flaw.

Risk and Exploitability

The CVSS score of 9.1 signals a high severity vulnerability, while the EPSS score is not available, so the precise likelihood of exploitation is uncertain. However, the flaw is listed in no KEV catalog, indicating no known publicly exploited incidents yet. Exploitation would occur over a network connection and requires the attacker to obtain or compromise the enclave TLS private key, after which the forged attestation can be used to bypass authentication checks on any relying party trusting the RA‑TLS chain.

Remediation

No solution or workaround provided in the CVE record.

OpenCVE Recommended Actions

  • Upgrade Enclave OS Virtual to tdx-v0.2.43 or tdx-gpu-v0.6.27 to apply the TLS‑session binding fix.
  • If an upgrade is delayed, ensure that the enclave TLS private key is stored securely and rotate it immediately, mitigating the risk of key compromise.
  • Verify that all exposure points appropriately validate the attestation binding before accepting a connection, and monitor for anomalous session behaviors that could indicate replay or spoofing attempts.

Generated by OpenCVE AI on October 9, 2026 at 22:21 UTC.

Tracking

Sign in to view the affected projects.

Advisories

No advisories available
History
Type Values Removed Values Added
Metrics ssvc

{'options': {'Automatable': 'no', 'Exploitation': 'none', 'Technical Impact': 'total'}, 'version': '2.0.3'}

Type Values Removed Values Added
First Time appeared Privasys
Privasys enclave-os-virtual
Vendors & Products Privasys
Privasys enclave-os-virtual
Type Values Removed Values Added
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.
Title enclave-os-virtual: RA-TLS challenge certificates were not bound to the TLS session
Weaknesses CWE-346
References
Metrics cvssV4_0

{'score': 9.1, 'vector': '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'}

Weaknesses

Sources

Status
PUBLISHED
Assigner
GitHub_M
Published
Updated
Oct 13, 2026, 11:31 AM
Reserved
Oct 9, 2026, 5:33 PM
Status
Deferred
Published
Oct 9, 2026, 10:16 PM
Modified
Oct 16, 2026, 8:04 PM