CVE-2026-108361 Privasys Intra-handshake attested TLS implementation is vulnerable to TOCTOU Attacks
Local attackers can modify workload state after TLS attestation due to a TOCTOU race, bypassing security checks in Privasys ra-tls-clients.
- Exploited in the wild
- Not known
- Login needed
- Any signed-in user
- Attackable
- Local or same network only
- Victim action needed
- Not needed
- Fix
- None listed
What is CVE-2026-108361?
CVE-2026-108361 is a high-severity vulnerability in Privasys ra-tls-clients, published on 12 Oct 2026. It can only be exploited from the same machine or local network, with no action from the victim.
Official description
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.
Weakness: CWE-367
Which versions are affected by CVE-2026-108361?
How do I fix CVE-2026-108361?
No fix has been published for CVE-2026-108361 yet. Limit exposure of the affected software until one is available.
Is CVE-2026-108361 being exploited?
There is no known exploitation of CVE-2026-108361 in the wild and no public exploit code.
Sources
Also known as GHSA-gg8q-mfhh-wrrc.