Is CVE-2026-108266 exploited in the wild?

No. Junglewise Threat Intelligence has no report of CVE-2026-108266 being exploited in the wild.

How severe is CVE-2026-108266?

Informational severity, published 9 October 2026.

Which products and versions are affected?

Privasys Rustls before privasys-v0.8.1.

Is there a fix for CVE-2026-108266?

Yes: fixed in privasys-v0.8.1. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.

How is CVE-2026-108266 attacked?

It is attacked over the network.

Am I affected by CVE-2026-108266?

Check whether you run Privasys Rustls at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

CVE-2026-108266: Privasys rustls RA-TLS relay attack in certificate binding

CVE-2026-108266 · Severity: info · Published 2026-10-09

Privasys rustls is a TLS library extension that adds remote attestation support for secure enclaves. An attacker with a stolen enclave TLS key could relay valid attestation certificates to impersonate the enclave on different connections, bypassing security checks that rely on session-specific attestation. This attack allows an attacker to falsely prove they control an attested enclave.

Vendors: Privasys.

Quick answers

Is CVE-2026-108266 exploited in the wild?: No. Junglewise Threat Intelligence has no report of CVE-2026-108266 being exploited in the wild.
How severe is CVE-2026-108266?: Informational severity, published 9 October 2026.
Which products and versions are affected?: Privasys Rustls before privasys-v0.8.1.
Is there a fix for CVE-2026-108266?: Yes: fixed in privasys-v0.8.1. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
How is CVE-2026-108266 attacked?: It is attacked over the network.
Am I affected by CVE-2026-108266?: Check whether you run Privasys Rustls at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

How to fix

Fixed in: privasys-v0.8.1

Technical details

Prior to v0.8.1, the RA-TLS challenge certificates bound the attestation quote's ReportData to the certificate public key and client nonce, but not to the active TLS session. An attacker who obtained an enclave TLS private key could relay a genuine quote onto another connection, causing relying parties to accept the attacker-terminated connection as the attested enclave. The fix derives a 32-byte channel binder from the TLS 1.3 key schedule (HKDF-Expand-Label) and commits it to both server and client certificate quotes, preventing relay attacks.

Affected products

Privasys rustls before privasys-v0.8.1

Timeline

2026-10-09: disclosed
2026-07-10: patched: Fix committed prior to disclosure

References

This page as Markdown. Free to reuse under CC BY 4.0 with a link back.