GPU VulnDB

Database/Firmware, BMC & network fabric

Enclave OS Virtual: RA-TLS quote not bound to the TLS session, so an attestation can be relayed

CVSS 9.1CVE-2026-108268Firmware, BMC & network fabriccurated

Impact

Enclave OS Virtual runs container workloads inside Intel TDX confidential VMs, and the tdx-gpu variant is the path operators use to give a tenant an attested confidential GPU. The RA-TLS certificate issuer put only the certificate public-key hash and the client nonce into the TDX quote's ReportData, with nothing tied to the live TLS session. Anyone who has obtained an enclave TLS private key can therefore replay a genuine quote onto a connection they terminate themselves, and the relying party accepts that connection as the attested enclave. The whole value of confidential GPU serving is that the tenant can prove what is on the other end of the channel; here the proof can be lifted onto an attacker-held channel, so model weights and prompts can be sent to a man in the middle that still passes attestation.

Who can reach it

Network attacker who can terminate a TLS connection to a relying party and who already holds an enclave TLS private key. No authentication to the enclave itself is needed; obtaining the key is the precondition, which is why NVD scores attack complexity high.

What to do

Upgrade to tdx-v0.2.43, or tdx-gpu-v0.6.27 for the GPU variant, and redeploy the confidential VMs and the relying-party verifier together - an upgraded enclave with an old verifier still accepts relayed quotes. Rotate any enclave TLS keys you cannot prove were never exposed. Workload restart is required; the host and the GPU firmware are not touched.

References

https://nvd.nist.gov/vuln/detail/CVE-2026-108268https://github.com/Privasys/enclave-os-virtual/security/advisories/GHSA-p5fp-g94g-g9m9https://github.com/Privasys/enclave-os-virtual/commit/9a6be91e29f2b6738d0b77c33cd1ad5cd3d8a347https://github.com/Privasys/enclave-os-virtual/releases/tag/tdx-gpu-v0.6.27

Related entries

All Firmware, BMC & network fabric entries

This entry is curated: imported from vendor advisories with machine assistance, not yet individually verified. Confirm against your vendor's advisory before acting, and report anything wrong.