CVE-2026-108362

CriticalCVSS 9.1

Published: 12/10/2026(UTC)Translated: 13/10/2026(UTC)NVD NIST

Summary

In Privasys Remote Attestation TLS Clients prior to 0.11.0, TEE attestation evidence is accepted without requiring an explicitly authorized platform identity. A network attacker can forge evidence or extract attestation secrets from a compromised unrevoked platform, causing the verifier to accept valid measurements from a different unrevoked TEE platform as though they came from the intended Attester. This allows impersonation of the attested TLS endpoint.

Risk Assessment

The organization may accept a TLS connection as originating from a trusted platform when it actually comes from an attacker, leading to a breach of communication confidentiality and integrity.

Recommendation

Update Privasys Remote Attestation TLS Clients to version 0.11.0 or later, which enforces explicit platform identity authorization.

Other vulnerabilities in Privasys Remote Attestation TLS Clients

CVE-2026-108361High
Privasys Remote Attestation TLS Clients before 0.9.1 performs attestation only once, at connection establishment time. An attacker with local access can modify workload code, data, and configuration at any time after the connection is established, while the verifying peer continues to trust the initial Evidence.

Original NVD description (English source)

Privasys Remote Attestation TLS Clients provides multi-language utilities for verifying attested TLS connections. Prior to 0.11.0, TEE attestation evidence in Privasys attested TLS is accepted without requiring an explicitly authorized platform identity. When a network attacker can forge evidence or extract attestation secrets from a compromised unrevoked platform, the verifier accepts valid measurements from a different unrevoked TEE platform as though they came from the intended Attester. The attacker can impersonate the attested TLS endpoint. This issue is fixed in version 0.11.0.

Vulnerability data from NVD (NIST) · CISA KEV · EPSS