# CVE-2026-108268: enclave-os-virtual: RA-TLS challenge certificates were not bound to the TLS session

> Attackers can bypass remote attestation in Enclave OS Virtual by relaying quotes, allowing them to impersonate attested enclaves.

- **Severity:** Critical 9.1 (`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`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 9 Oct 2026
- **Updated:** 13 Oct 2026
- **Also known as:** GHSA-p5fp-g94g-g9m9

## What is CVE-2026-108268?

CVE-2026-108268 is a critical vulnerability in Privasys enclave-os-virtual, published on 9 Oct 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official 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.

Weakness: CWE-346 (Origin Validation Error)

## Which versions are affected by CVE-2026-108268?


## How do I fix CVE-2026-108268?

No fix has been published for CVE-2026-108268 yet. Limit exposure of the affected software until one is available.

## Is CVE-2026-108268 being exploited?

There is no known exploitation of CVE-2026-108268 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-108268 and fix it if it is affected.

What it is: CVE-2026-108268 is a critical vulnerability in Privasys enclave-os-virtual, published on 9 Oct 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-108268 in the wild and no public exploit code.

Affected product: Privasys enclave-os-virtual. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-108268/ (Markdown: https://insights.sbomify.com/CVE-2026-108268/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-108268
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-108268
- OSV: https://osv.dev/vulnerability/CVE-2026-108268

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-108268/
Summaries are generated and may contain mistakes; the official description above is the record.