CVE-2026-108267 Privasys Go fork: RA-TLS challenge mode did not bind attestation evidence to the TLS session
Attackers can bypass remote attestation in Privasys Go by relaying quotes, allowing unverified connections to appear as attested enclaves.
- Exploited in the wild
- Not known
- Login needed
- Not needed
- Attackable
- Over the internet
- Victim action needed
- Not needed
- Fix
- None listed
What is CVE-2026-108267?
CVE-2026-108267 is a critical vulnerability in Privasys go, published on 9 Oct 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.
Official description
Privasys Go is a maintained fork of the Go programming language that adds RA-TLS support to crypto/tls. Prior to privasys-v0.5.1-go1.26.5, challenge-mode RA-TLS certificates bound quote ReportData to the certificate public key and client nonce but not to the active TLS session. An attacker who obtained an enclave TLS private key could relay a genuine quote onto another connection, causing a relying party to accept a handshake terminated by the attacker as an attested enclave connection. This issue is fixed in privasys-v0.5.1-go1.26.5.
Weakness: CWE-346
Which versions are affected by CVE-2026-108267?
How do I fix CVE-2026-108267?
No fix has been published for CVE-2026-108267 yet. Limit exposure of the affected software until one is available.
Is CVE-2026-108267 being exploited?
There is no known exploitation of CVE-2026-108267 in the wild and no public exploit code.
Sources
Also known as AZL-107973, AZL-107982, AZL-107985, AZL-107997, AZL-108006, GHSA-7jfw-53rm-phh2.