CVE-2026-108362

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.

• https://github.com/Privasys/ra-tls-clients/commit/1179ed097fdcb8519a85973a8a6c6ccbd0f50b03
• https://github.com/Privasys/ra-tls-clients/releases/tag/v0.11.0
• https://github.com/Privasys/ra-tls-clients/security/advisories/GHSA-pj2x-5wqv-fh57

• https://github.com/Privasys/ra-tls-clients/commit/1179ed097fdcb8519a85973a8a6c6ccbd0f50b03
• https://github.com/Privasys/ra-tls-clients/releases/tag/v0.11.0
• https://github.com/Privasys/ra-tls-clients/security/advisories/GHSA-pj2x-5wqv-fh57

• HIGHCVE-2026-100598PoC
• HIGHCVE-2026-100642PoC
• HIGHCVE-2026-100646PoC
• HIGHCVE-2026-100803
• HIGHCVE-2026-100809
• HIGHCVE-2026-100816
• MEDIUMCVE-2026-100821
• HIGHCVE-2026-100830

Related by shared AI tags and CWE weakness class. Browse the full archive.