Vulnerability · Published Oct 9, 2026 · Assigned by GitHub_M

CVE-2026-108267Privasys Go fork: RA-TLS challenge mode did not bind attestation evidence to the TLS session

Critical 9.1

In plain English

A critical-severity security flaw in go from Privasys. There are no confirmed reports of exploitation so far. The chance it is exploited in the next 30 days is estimated at 0.1% (higher than 2% of all known vulnerabilities).

Severity (CVSS 4.0)9.1Critical

Exploit odds (30 days)0.1%top 98.3% of all CVEs

Exploited in the wildNo reportsCISA SSVC: none

Attack toolingNoneno public tooling known

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.

Affected products (as reported)

Vendor	Product	Versions
Privasys	go	< privasys-v0.5.1-go1.26.5

Weakness: CWE-346 · Vector: CVSS:4.0/AV:N/AC:H/AT:P/PR:N/UI:N/VC:H/VI:H/VA:N/SC:N/SI:N/SA:N

References

https://github.com/Privasys/go/security/advisories/GHSA-7jfw-53rm-phh2 x_refsource_CONFIRM
https://github.com/Privasys/go/commit/00a7d21ba53bba0ea09ac7a67eb2c6714e651700 x_refsource_MISC
https://github.com/Privasys/go/releases/tag/privasys-v0.5.1-go1.26.5 x_refsource_MISC
https://privasys.org/blog/binding-attestation-to-the-tls-session x_refsource_MISC