Organisations at risk: Privasys SGX apps face integrity loss from TLS quote relay flaw

Organisations relying on Privasys Enclave OS Mini for confidential computing face a severe security risk due to a critical remote attestation bypass vulnerability. National Vulnerability Database records identify CVE-2026-108265 as a critical severity issue affecting versions of the Rust-based runtime before wasm-v0.40.0. This flaw allows malicious actors to undermine the trust model of Intel SGX enclaves, potentially exposing sensitive data processed within these isolated environments.

The vulnerability exists within the Remote Attestation over TLS (RA-TLS) challenge certificate path. According to the NVD description, the implementation placed the certificate public-key hash and client nonce in the quote ReportData but failed to bind a value to the active TLS session. This omission creates a window for relay attacks, where an attacker can intercept and redirect legitimate attestation quotes to different connections, tricking relying parties into trusting compromised endpoints.

What we know

The core issue lies in how the SGX runtime handles cryptographic proofs during the attestation process. Prior to the release of version wasm-v0.40.0, the Enclave OS Mini did not sufficiently tie the attestation quote to the specific TLS session in which it was generated. This lack of binding means that the cryptographic evidence of an enclave's identity is not uniquely attached to the communication channel.

An attacker who obtains an enclave TLS private key can exploit this gap. By capturing a genuine quote from a valid connection, the adversary can relay this quote onto a separate, attacker-controlled connection. The relying party, expecting to communicate with the attested enclave, instead accepts the attacker-terminated connection as legitimate. This effectively bypasses the security guarantees provided by the Intel SGX hardware.

The weakness is categorised under CWE-346, which relates to insufficient verification of data authenticity. The Common Vulnerability Scoring System rates this flaw at 9.1, indicating critical severity. This high score reflects the ease of exploitation and the potential impact on confidentiality and integrity. The issue has been resolved in the wasm-v0.40.0 release of the Enclave OS Mini runtime.

Defender's checklist

• Verify the current version of Privasys Enclave OS Mini deployed in your infrastructure to check for exposure.
• Review network logs for unusual TLS termination patterns or unexpected attestation quote reuses.
• Ensure that all relying parties strictly validate the TLS session binding during the attestation process.
• Audit access controls for enclave TLS private keys to prevent unauthorised extraction or use.

What to do and how to stay safe: Privasys

• Inventory all systems running Privasys Enclave OS Mini and identify any instances using versions older than wasm-v0.40.0.
• Monitor network traffic for anomalies in TLS handshake patterns that could indicate relay attempts or session hijacking.
• Update your security policies to require strict validation of attestation quotes against the active TLS session context.
• Prepare deployment procedures to update to wasm-v0.40.0 once the vendor provides an update and testing confirms compatibility.

Step-by-step guide: Virtual Patching: Benefits, Limits and When to Use It

General security guidance from the TechWire Beat newsroom. It is not confirmed advice from the organisations named in this story.

Frequently asked questions

Which versions of Privasys Enclave OS Mini are affected by CVE-2026-108265?

All versions of Enclave OS Mini prior to wasm-v0.40.0 are affected by this critical vulnerability.

What is the primary impact of this vulnerability?

Attackers can relay genuine attestation quotes to different connections, causing relying parties to accept attacker-terminated connections as the attested enclave.

Has a fix been released for this issue?

Yes, the issue is fixed in version wasm-v0.40.0 of the Enclave OS Mini runtime.