CVE-2026-108269: ra-tls-clients: RA-TLS challenge verifier accepted quotes not bound to the TLS session
Remote Attestation TLS Clients provides multi-language utilities for verifying attested TLS connections. Prior to 0.5.0, the Rust and Go RA-TLS challenge verifiers accepted quote ReportData that was bound to the certificate public key and client nonce but not to the active TLS session before permitting application traffic. An attacker who obtained an enclave TLS private key could relay a genuine quote onto another connection, causing the clients to accept an attacker-terminated connection as the attested enclave. This issue is fixed in 0.5.0.
Affected Software
Remediation
Recommended actions to resolve this vulnerability, in priority order.
- Upgrade
Upgrade
ra-tls-clientsto a version that resolves this vulnerability.Fixed in 0.5.0
Event History
Frequently Asked Questions
Which implementations are affected?
The Rust and Go RA-TLS challenge verifiers are affected in versions prior to 0.5.0.
What does an attacker need to exploit this issue?
The attacker needs to obtain an enclave TLS private key and a genuine quote. They can then relay that quote to a separate connection that they terminate, making the client accept it as the attested enclave.
Are connections protected by the verifier vulnerable by default?
The issue affects the challenge-verification behavior described for the Rust and Go clients before 0.5.0, because quote ReportData was not bound to the active TLS session before application traffic was allowed.
What is the remediation?
Upgrade Remote Attestation TLS Clients to version 0.5.0, which fixes the missing binding between the quote and the active TLS session.