The vulnerability stems from the RA‑TLS challenge certificate path not including a value bound to the active TLS session. As a result, an attacker who can obtain the enclave’s TLS private key can relay a legitimate quote over a different connection and convince a relying party that the connection is authenticated to the intended enclave. This bypasses the attestation’s integrity guarantees and effectively allows a man‑in‑the‑middle that can masquerade as the enclave, potentially exposing confidential data or altering transaction integrity. The weakness is a classic missing binding of a security token to its context, classified as CWE‑346.

The affected software is Privasys enclave‑os‑mini, a Rust‑based runtime for Intel SGX enclaves. All releases before version wasm‑v0.40.0 are vulnerable, including every commit prior to the 0.40.0 release. The fix was introduced in that release and is available in the corresponding GitHub tag and release assets.

With a CVSS score of 9.1 this issue is considered critical. The EPSS data is not available, so exploitation probability cannot be quantified, and it is not listed in the CISA KEV catalog. The attack likely requires remote network access to the TLS endpoint and possession of the enclave’s TLS private key, a credential that could be obtained if key material is improperly protected or exposed. Once those prerequisites are met, the attacker can re‑use the same quote and forge an authenticated session, leading to severe confidentiality and integrity impacts for all relying parties.