Key points
- Privasys released wasm-v0.40.0 to fix CVE-2026-108265, rated CVSS 9.1.
- The flaw allowed attackers to relay valid quotes to different connections.
- Older versions omitted TLS session binding in the quote ReportData.
Privasys has released a security update for its Enclave OS Mini runtime to address a critical vulnerability that compromises the integrity of Intel SGX attestation. The fix, included in version wasm-v0.40.0, resolves CVE-2026-108265, which carries a CVSS score of 9.1. This update is essential for any organization relying on the affected Rust-based runtime for confidential applications, as the flaw allowed attackers to bypass standard verification checks.
In plain English
Enclave OS Mini helps run sensitive applications inside secure Intel SGX enclaves. To prove an enclave is genuine, it creates a digital quote. Before version wasm-v0.40.0, this quote included the public key hash and a client nonce in the ReportData field. However, it failed to include a value tied to the specific active TLS session, leaving the verification process open to manipulation by sophisticated attackers.
The background
According to the National Vulnerability Database, this issue stems from CWE-346, a design weakness in how cryptographic protocols are handled. Because the quote did not bind to the active TLS session, an attacker who obtained the enclave's TLS private key could take a genuine quote and relay it to a different connection. This tricked relying parties into accepting the attacker-terminated connection as if it were the original, attested enclave.
What changes now
Privasys has confirmed that the issue is resolved in Enclave OS Mini version wasm-v0.40.0. Users running versions prior to wasm-v0.40.0 are affected by this critical vulnerability. The vendor’s patch ensures that the quote ReportData now properly binds to the active TLS session, preventing the relay of valid quotes to unauthorized connections and restoring the integrity of the attestation process.
What to do and how to stay safe: Privasys
- Audit your infrastructure to identify any instances of Privasys Enclave OS Mini running versions older than wasm-v0.40.0.
- Upgrade affected systems to wasm-v0.40.0 or later as soon as possible to close the attestation bypass vulnerability.
- Review logs for unusual TLS connection patterns that might indicate an attacker relaying quotes to unauthorized endpoints.
- Verify that your relying parties are correctly validating the TLS session binding in incoming enclave quotes.
Step-by-step guide: Emergency Patching: How to Fix Critical Flaws Without Breaking Systems
General security guidance from the Patch Review newsroom. It is not confirmed advice from the organisations named in this story.
Frequently asked questions
What is CVE-2026-108265?
It is a critical vulnerability in Privasys Enclave OS Mini prior to wasm-v0.40.0 that allows relay attacks on SGX attestation.
Which versions are affected?
All versions of Privasys Enclave OS Mini prior to wasm-v0.40.0 are affected by this flaw.
How was the vulnerability fixed?
The fix in wasm-v0.40.0 adds a value bound to the active TLS session in the quote ReportData.
