CVE-2026-108265GHSA-49qm-4pj3-w2c6
enclave-os-mini: RA-TLS challenge certificates were not bound to the TLS session
Privasys enclave-os-mini
CVSS
9.1CriticalExploitationNo known exploitationNot in CISA KEV, which does not prove it is unexploitedCISA KEV
Exploit odds (EPSS)0.12%Chance of exploitation activity in the next 30 days, higher than 1% of CVEs. Scored 23 Oct 2026FIRST EPSS
Fixed inNone listedNo source names a fixed version. Check the vendor advisory below
What fixes it
No source in this snapshot names a fixed version. The vendor advisories under References are the place to check.
Description
Enclave OS Mini is a Rust-based runtime for confidential applications inside Intel SGX enclaves. Prior to wasm-v0.40.0, the SGX runtime's RA-TLS challenge certificate path 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 wasm-v0.40.0.
Text from CVE List
Affected versions 1
- enclave-os-miniaffected: < wasm-v0.40.0CVE List
References 4
- github.com/Privasys/enclave-os-mini/commit/9f541c849ef733d2df2851a666f359d01dcdcb8eFixvia CVE List
- github.com/Privasys/enclave-os-mini/releases/tag/wasm-v0.40.0Fixvia CVE List
- github.com/Privasys/enclave-os-mini/security/advisories/GHSA-49qm-4pj3-w2c6Advisoryvia CVE List
- privasys.org/blog/binding-attestation-to-the-tls-sessionReferencevia CVE List