Is CVE-2026-108362 exploited in the wild?

No. Junglewise Threat Intelligence has no report of CVE-2026-108362 being exploited in the wild.

How severe is CVE-2026-108362?

Informational severity, published 12 October 2026.

Which products and versions are affected?

Privasys Remote Attestation TLS Clients before 0.11.0.

Is there a fix for CVE-2026-108362?

Yes: fixed in 0.11.0. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.

How is CVE-2026-108362 attacked?

It is attacked over the network, in a software library.

Am I affected by CVE-2026-108362?

Check whether you run Privasys Remote Attestation TLS Clients at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

CVE-2026-108362: Privasys Remote Attestation TLS Clients platform identity bypass

CVE-2026-108362 · Severity: info · Published 2026-10-12

Privasys Remote Attestation TLS Clients is a library for verifying that TLS connections originate from trusted hardware enclaves. Prior to version 0.11.0, the library failed to enforce that attestation evidence came from an explicitly authorized platform identity. An attacker who can forge attestation evidence or compromise an unrevoked enclave can impersonate the intended TLS endpoint, allowing account takeover or data exposure.

Technologies: Privasys Remote Attestation TLS Clients. Vendors: Privasys.

Quick answers

Is CVE-2026-108362 exploited in the wild?: No. Junglewise Threat Intelligence has no report of CVE-2026-108362 being exploited in the wild.
How severe is CVE-2026-108362?: Informational severity, published 12 October 2026.
Which products and versions are affected?: Privasys Remote Attestation TLS Clients before 0.11.0.
Is there a fix for CVE-2026-108362?: Yes: fixed in 0.11.0. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
How is CVE-2026-108362 attacked?: It is attacked over the network, in a software library.
Am I affected by CVE-2026-108362?: Check whether you run Privasys Remote Attestation TLS Clients at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

How to fix

Fixed in: 0.11.0

Technical details

The verifier failed to require an authorized platform identity when accepting TEE attestation evidence, allowing an attacker to forge evidence or extract secrets from a compromised platform and present valid measurements from a different unrevoked TEE as if they came from the intended Attester. The fix in 0.11.0 introduces a platform allow-list mechanism in the VerificationPolicy, comparing the platform identity from PCK certificates (Platform Instance ID, PPID for Intel SGX/TDX; CHIP_ID for AMD SEV-SNP) against authorized identifiers, with enforcement on both SDK and server side.

Affected products

Privasys Remote Attestation TLS Clients before 0.11.0

Timeline

2026-10-12: disclosed
2026-09-06: patched

References

This page as Markdown. Free to reuse under CC BY 4.0 with a link back.