Privasys rustls v0.8.1 patches CVE-2026-108266 to stop quote relay attacks that bypass enclave attestation
A critical vulnerability in Privasys rustls allowed attackers to bypass enclave attestation via quote relay, now resolved in version 0.8.1.
Key points
- CVE-2026-108266 allows relay of genuine quotes to bypass attestation checks.
- The flaw affects Privasys rustls versions prior to privasys-v0.8.1.
- Attackers can impersonate attested enclaves if they obtain the TLS private key.
Privasys rustls, a maintained fork of the rustls TLS library, addressed a critical security flaw in its RA-TLS challenge implementation. The vulnerability, tracked as CVE-2026-108266, stems from insufficient binding of quote ReportData to the active TLS session. This weakness allowed attackers to relay genuine quotes, undermining the integrity of remote attestation processes for relying parties.
Root cause
The issue arises because RA-TLS challenge certificates emitted by affected versions bind the quote ReportData only to the certificate public key and client nonce. According to the NVD record, the data was not bound to the active TLS session. This missing cryptographic link creates a window where a quote can be detached from its original context and reused elsewhere without detection.
Attack path
An attacker must first obtain the enclave TLS private key to exploit this flaw. Once in possession of the key, the adversary can capture a genuine quote from a legitimate connection. They then relay this quote onto a different, attacker-terminated connection. The relying party accepts the connection as the attested enclave because the quote appears valid, despite the session mismatch.
Affected versions
Privasys rustls versions prior to privasys-v0.8.1 are affected by this vulnerability. The National Vulnerability Database rates CVE-2026-108266 as Critical with a CVSS score of 9.1. The weakness is classified under CWE-346, indicating a failure to bind the cryptographic operation to the correct context.
Mitigation
- Upgrade Privasys rustls to version privasys-v0.8.1 or later immediately.
- Audit systems relying on RA-TLS for evidence of quote relay attempts.
- Review TLS session logs for anomalies in quote binding validation.
Background: CVSS score
The Common Vulnerability Scoring System provides a standardised method to rank flaw severity. It enables teams to prioritise remediation efforts based on exploitability and impact. However, the score is a static snapshot that ignores your specific architecture. You must combine it with context-aware analysis to make accurate risk decisions.
Read the full guide: Why CVSS Scores Matter for Real-World Security Decisions
What to do and how to stay safe: Privasys
- Identify all instances of Privasys rustls in your software supply chain.
- Verify that current versions are below privasys-v0.8.1 to assess risk.
- Monitor network traffic for unusual TLS connection patterns involving attestation.
- Plan upgrades to the patched version once the vendor provides an update.
General security guidance from the TechSec Observer newsroom. It is not confirmed advice from the organisations named in this story.
Frequently asked questions
What is CVE-2026-108266?
It is a critical vulnerability in Privasys rustls that allows quote relay attacks by failing to bind quote data to the TLS session.
Which versions are affected?
All versions of Privasys rustls prior to privasys-v0.8.1 are vulnerable to this issue.
Is there a fix available?
Yes, the issue is fixed in Privasys rustls version privasys-v0.8.1.
