13 matches found
CVE-2026-108267
Privasys Go is a maintained fork of the Go programming language that adds RA-TLS support to crypto/tls. Prior to privasys-v0.5.1-go1.26.5, challenge-mode RA-TLS certificates bound quote ReportData to the certificate public key and client nonce but not to the active TLS session. An attacker who...
CVE-2026-108268
Enclave OS Virtual runs container workloads inside confidential virtual machines with end-to-end attestation. Prior to tdx-v0.2.43 and tdx-gpu-v0.6.27, the TDX/GPU RA-TLS certificate issuer placed the certificate public-key hash and client nonce in quote ReportData but omitted a value bound to th...
CVE-2026-108266
Privasys rustls is a maintained fork of the rustls TLS library that adds RA-TLS challenge and channel-binding support. Prior to privasys-v0.8.1, the fork emitted RA-TLS challenge certificates whose quote ReportData was bound to the certificate public key and client nonce but not to the active TLS...
CVE-2026-108265
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...
CVE-2026-108269
Prior to version 0.5.0 , the Rust and Go challenge verifiers in Remote Attestation TLS Clients are vulnerable to an Origin Validation Error (CWE-346). The flaw exists because the verifiers accepted quote ReportData bound only to the certificate public key and client nonce, rather than the active ...
CVE-2026-108268
Enclave OS Virtual contains a vulnerability where the TDX/GPU RA-TLS certificate issuer fails to include a value bound to the active TLS session within the quote ReportData . This omission allows an attacker who possesses an enclave TLS private key to relay a genuine quote to a different connecti...
CVE-2026-108267
The Privasys Go programming language fork, which provides RA-TLS support for crypto/tls , is vulnerable in versions prior to privasys-v0.5.1-go1.26.5 . In challenge-mode RA-TLS, certificates failed to bind quote ReportData to the active TLS session, binding it only to the certificate public key a...
CVE-2026-108266 Privasys rustls fork: RA-TLS challenge mode did not bind attestation evidence to the TLS session
Privasys rustls is a maintained fork of the rustls TLS library that adds RA-TLS challenge and channel-binding support. Prior to privasys-v0.8.1, the fork emitted RA-TLS challenge certificates whose quote ReportData was bound to the certificate public key and client nonce but not to the active TLS...
EUVD-2026-95997
Privasys rustls is a maintained fork of the rustls TLS library that adds RA-TLS challenge and channel-binding support. Prior to privasys-v0.8.1, the fork emitted RA-TLS challenge certificates whose quote ReportData was bound to the certificate public key and client nonce but not to the active TLS...
CVE-2026-108266
The Privasys rustls library, a fork of rustls providing RA-TLS challenge and channel-binding support, is vulnerable in versions prior to privasys-v0.8.1 . The root cause is that RA-TLS challenge certificates emitted by the library bound quote ReportData to the certificate public key and client no...
CVE-2026-108265 enclave-os-mini: RA-TLS challenge certificates were not bound to the TLS session
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...
CVE-2026-108265
The Enclave OS Mini Rust-based runtime for Intel SGX enclaves contains a vulnerability in the RA-TLS challenge certificate path (prior to wasm-v0.40.0 ). The issue stems from the runtime placing the certificate public-key hash and client nonce in the quote ReportData while failing to include a va...
EUVD-2026-95996
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...