Read the docs
TI-2026-71258 Aliases CVE-2026-108362

Privasys attested TLS accepts evidence from other TEE platforms

Priority MEDIUM 40CWE-346Published · Updated

Key facts

Attack vector
Network
Privileges required
None
User interaction
None
Attack complexity
High
Attack requirements
Present
Impact type
Security bypass
Confidentiality · integrity · availability
High · High · None
Fix status
Fixed

Attack profile from CVSS 4.0 · CNA. Fix status from CNA. Impact type from CWE-346.

Summary

Privasys ra-tls-clients before 0.11.0 accepts TEE attestation evidence without requiring an explicitly authorized platform identity (CWE-346). A network attacker who can forge evidence or extract attestation secrets from a compromised unrevoked platform can make the verifier accept measurements from a different unrevoked TEE platform. The attacker can then impersonate the attested TLS endpoint.

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

Why it matters now

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

SSVC decision points

CISA ADP · SSVC 2.0.3

Exploitation
None
Automatable
No
Technical impact
Total

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.11.00.11.0Patch availableCNA
  • ra-tls-clients VendorPrivasys Affected before 0.11.0 Fixed in 0.11.0 Patch available CNA

Remediation

Upgrade Privasys ra-tls-clients to version 0.11.0, which fixes this issue.

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

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

Timeline

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

References

Other 3

  • TI-2026-70299 Privasys rustls RA-TLS attestation not bound to the TLS session 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
  • TI-2026-71257 Privasys ra-tls-clients trusts stale attestation after TLS setup CVSS 4.0HIGH 7.2

Sources

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