CVE-2026-108361

HighCVSS 7.2

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

Summary

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.

Risk Assessment

The organization may rely on stale attestation state, allowing modified code to run on an attested endpoint undetected. This undermines trust mechanisms and can lead to compromise of protected resources.

Recommendation

Update Privasys/ra-tls-clients to version 0.9.1 or later, which fixes the vulnerability. Until patched, restrict local access to endpoints acting as the Attester.

Other vulnerabilities in Privasys Remote Attestation TLS Clients

CVE-2026-108362Critical
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.

Original NVD description (English source)

Privasys Remote Attestation TLS Clients provides multi-language utilities for verifying attested TLS connections. Before 0.9.1, an attacker with local access could modify workload code, data, and configuration at any time after successful connection establishment. Once Evidence was successfully appraised and the connection was established, there was a window of vulnerability from the establishment of the connection to the termination of the connection where an attacker could modify the state of the workload and platform at runtime on the TLS endpoint acting as the Attester. This vulnerability was possible because Privasys/ra-tls-clients performed attestation only once in the lifetime of the connection (at connection establishment time), and the verifying peer continued to believe that the state was the same as in the initial Evidence throughout, whereas it could be stale at some point in time. This vulnerability is fixed in 0.9.1.

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