Read the docs
TI-2026-71257 Aliases CVE-2026-108361

Privasys ra-tls-clients trusts stale attestation after TLS setup

Priority LOW 30CWE-367Published · Updated

Key facts

Attack vector
Local
Privileges required
Low
User interaction
None
Attack complexity
Low
Attack requirements
Present
Impact type
—
Confidentiality · integrity · availability
High · High · None
Fix status
Fixed

Attack profile from CVSS 4.0 · CNA. Fix status from CNA.

Summary

Privasys ra-tls-clients before 0.9.1 performs attestation only once, when the TLS connection is established. A local attacker with low privileges can modify workload code, data, or configuration at runtime afterward, while the verifying peer still trusts the initial evidence. The flaw is a time-of-check time-of-use race condition (CWE-367).

Written with Claude Haiku 5.5 from the sources below · 2026-10-29

Description from the CNA

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.

Why it matters now

Exploitation None reported CISA SSVC · not in CISA KEV
EPSS 0.00085 0th percentileScored 2026-11-07
Fix Fixed ra-tls-clients (Privasys): 0.9.1

SSVC decision points

CISA ADP · SSVC 2.0.3

Exploitation
None
Automatable
No
Technical impact
Partial

The decision (Track, Attend, Act) also depends on your mission and well-being impact; see CISA's SSVC guide.

Affected products

VendorProductAffected versionsFixed inStatusSource
Privasysra-tls-clientsbefore 0.9.10.9.1Patch availableCNA
  • ra-tls-clients VendorPrivasys Affected before 0.9.1 Fixed in 0.9.1 Patch available CNA

Remediation

Update Privasys ra-tls-clients to version 0.9.1, which fixes this flaw.

Written with Claude Haiku 5.5 from the sources below · 2026-10-29

  • Fix · CNA ra-tls-clients (Privasys) Fixed in 0.9.1

Timeline

  1. 2026-10-12 Threatist record created from CVE-2026-108361
  2. 2026-10-13 Priority changed: MEDIUM → LOW
  3. 2026-10-16 CISA SSVC decision points changed

References

Other 4

  • TI-2026-70299 Privasys rustls RA-TLS attestation not bound to the TLS session CVSS 4.0CRITICAL 9.1
  • TI-2026-71258 Privasys attested TLS accepts evidence from other TEE platforms CVSS 4.0CRITICAL 9.1
  • TI-2026-70301 Privasys enclave-os-virtual RA-TLS quotes not bound to TLS session CVSS 4.0CRITICAL 9.1
  • TI-2026-70300 Privasys Go RA-TLS attestation not bound to the TLS session CVSS 4.0CRITICAL 9.1
  • TI-2026-70298 enclave-os-mini RA-TLS certificates not bound to TLS session CVSS 4.0CRITICAL 9.1
  • TI-2026-70302 RA-TLS challenge verifier in ra-tls-clients accepts relayed quotes CVSS 4.0CRITICAL 9.1

Sources

This product uses the NVD API but is not endorsed or certified by the NVD. Sources and licences