# CVE-2026-108362: Privasys attested TLS accepted evidence from any unrevoked TEE platform (diversion attack)

> Attackers can impersonate attested TLS endpoints by using valid evidence from any unrevoked TEE platform, bypassing identity verification.

- **Severity:** Critical 9.1 (`CVSS:4.0/AV:N/AC:H/AT:P/PR:N/UI:N/VC:H/VI:H/VA:N/SC:N/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 12 Oct 2026
- **Updated:** 13 Oct 2026
- **Also known as:** GHSA-pj2x-5wqv-fh57

## What is CVE-2026-108362?

CVE-2026-108362 is a critical authentication bypass vulnerability in Privasys ra-tls-clients, published on 12 Oct 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

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.

Weakness: CWE-346 (Origin Validation Error)

## Which versions are affected by CVE-2026-108362?


## How do I fix CVE-2026-108362?

No fix has been published for CVE-2026-108362 yet. Limit exposure of the affected software until one is available.

## Is CVE-2026-108362 being exploited?

There is no known exploitation of CVE-2026-108362 in the wild and no public exploit code.

## Fix prompt for AI coding agents

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

What it is: CVE-2026-108362 is a critical authentication bypass vulnerability in Privasys ra-tls-clients, published on 12 Oct 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-108362 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-108362/ (Markdown: https://insights.sbomify.com/CVE-2026-108362/index.md)
```

## Sources

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

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