# 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.

- **Severity:** High 7.2 (`CVSS:4.0/AV:L/AC:L/AT:P/PR:L/UI:N/VC:H/VI:H/VA:N/SC:N/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 12 Oct 2026
- **Updated:** 15 Oct 2026
- **Also known as:** GHSA-gg8q-mfhh-wrrc

## 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 (Time-of-check Time-of-use (TOCTOU) Race Condition)

## 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.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-108361 and fix it if it is affected.

What it is: 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.
Exploitation: There is no known exploitation of CVE-2026-108361 in the wild and no public exploit code.

Affected product: Privasys ra-tls-clients. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-108361/ (Markdown: https://insights.sbomify.com/CVE-2026-108361/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-108361
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-108361
- OSV: https://osv.dev/vulnerability/CVE-2026-108361

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-108361/
Summaries are generated and may contain mistakes; the official description above is the record.