Key points
- CVE-2026-108362 is rated Critical with a CVSS score of 9.1.
- Attackers could impersonate attested TLS endpoints in versions prior to 0.11.0.
- The vulnerability stems from accepting TEE evidence without authorized platform identity checks.
The short version
- Privasys released version 0.11.0 to fix a critical security flaw.
- The bug allowed network attackers to spoof TLS endpoint identities.
- Versions before 0.11.0 accepted attestation evidence from unauthorized platforms.
The details
Privasys has addressed a critical vulnerability in its ra-tls-clients library by releasing version 0.11.0. The flaw, tracked as CVE-2026-108362, carries a CVSS score of 9.1, classifying it as Critical severity according to the National Vulnerability Database. This issue affected all versions of the software prior to the 0.11.0 release. The vulnerability is categorized under CWE-346, which relates to origin verification errors.
The core problem involved how the library handled Trusted Execution Environment (TEE) attestation evidence. Prior to the fix, the verifier accepted this evidence without requiring an explicitly authorized platform identity. This lack of strict identity validation created a significant security gap in the attested TLS connection process. Developers using older versions of the library were exposed to this risk.
The context
According to the NVD record, an attacker with network access could exploit this flaw to impersonate the attested TLS endpoint. This was possible if the attacker could forge attestation evidence or extract secrets from a compromised, unrevoked platform. The verifier would then accept valid measurements from a different unrevoked TEE platform as if they originated from the intended attester.
This behavior effectively allowed endpoint impersonation, undermining the trust model of the attested TLS connections. The ra-tls-clients library provides multi-language utilities for verifying these connections, making the flaw relevant to a broad range of applications relying on secure attestation. The fix in version 0.11.0 enforces the required identity checks.
What should you do?
Developers should immediately verify which version of Privasys ra-tls-clients their projects depend on. If the version is below 0.11.0, they must upgrade to the patched release to mitigate the impersonation risk. Teams should audit their dependency trees to ensure no transitive dependencies are pulling in vulnerable versions. Monitoring for further advisories from the vendor is also recommended.
What to do and how to stay safe: Privasys
- Check your project dependencies for Privasys ra-tls-clients versions older than 0.11.0.
- Update to version 0.11.0 or later to apply the fix for CVE-2026-108362.
- Review logs for any unusual TLS attestation failures or successes from unexpected platforms.
- Implement strict platform identity verification in custom attestation logic if applicable.
Step-by-step guide: Automatic Software Updates: 8 FAQs on Security and Risk
General security guidance from the DataSafe Times newsroom. It is not confirmed advice from the organisations named in this story.
Frequently asked questions
What is the CVSS score for CVE-2026-108362?
The National Vulnerability Database rates CVE-2026-108362 with a CVSS score of 9.1, which is Critical.
Which versions of Privasys ra-tls-clients are affected?
All versions of Privasys ra-tls-clients prior to 0.11.0 are affected by this vulnerability.
How did attackers exploit this flaw?
Attackers could forge evidence or extract secrets from compromised platforms to impersonate TLS endpoints, as the verifier accepted measurements without checking for authorized platform identity.
