Privasys RA-TLS Critical Relay Vulnerability Bypasses Session Binding in Rust/Go Enclaves

Privasys ra-tls-clients contains a critical remote attestation relay vulnerability identified as CVE-2026-108269. The flaw impacts the Rust and Go libraries used for verifying attested TLS connections. According to the National Vulnerability Database, the issue allows an attacker to bypass security controls by relaying a valid quote to a different connection. This enables an attacker-terminated connection to be accepted as a legitimate attested enclave.

Root cause

The vulnerability stems from incomplete binding in the challenge verification process within versions prior to 0.5.0. The RA-TLS challenge verifiers accepted quote ReportData that was bound to the certificate public key and the client nonce. However, the verifiers did not bind this data to the active TLS session before permitting application traffic. According to the NVD record, this missing binding creates a gap where the attestation proof is not strictly tied to the specific network session being verified.

Attack path

An attacker must first obtain the enclave TLS private key to exploit this weakness. With the private key, the attacker can capture a genuine quote generated by an enclave. The attacker then relays this genuine quote onto a different, attacker-controlled connection. Because the client verifies the quote against the public key and nonce but not the session, the client accepts the relayed quote. Consequently, the client treats the attacker-terminated connection as the attested enclave, allowing unauthorized access or data interception.

Affected versions

The vulnerability affects all versions of Privasys ra-tls-clients prior to version 0.5.0. This includes both the Rust and Go implementations of the library. The flaw is present in the core verification logic used by these multi-language utilities. Organizations using any version below 0.5.0 are exposed to this remote attestation bypass. The issue was addressed in the release of version 0.5.0.

Mitigation

• Update Privasys ra-tls-clients to version 0.5.0 or later.
• Verify that your build environment pulls the latest library dependencies.
• Audit existing deployments to identify any instances of older versions.
• Ensure that attestation verification includes strict session binding checks.

What to do and how to stay safe: Privasys

• Inventory all systems using Privasys ra-tls-clients to determine current versions.
• Check for updates to the library in your package manager or repository.
• Monitor network logs for unusual TLS handshake patterns or quote reuse.
• Review attestation policies to ensure session binding is enforced in all contexts.

Step-by-step guide: Attack Surface Management: 6 Common Misreadings and Correct Views

General security guidance from the NetSec Observer newsroom. It is not confirmed advice from the organisations named in this story.

Frequently asked questions

What is the CVSS score for CVE-2026-108269?

The National Vulnerability Database rates CVE-2026-108269 as CVSS 9.1, which is classified as critical.

Which programming languages are affected by this vulnerability?

The vulnerability affects the Rust and Go implementations of the Privasys ra-tls-clients library.

Is there a fix available for this issue?

Yes, the issue is fixed in Privasys ra-tls-clients version 0.5.0.