CVE-2026-108267Privasys Go fork: RA-TLS challenge mode did not bind attestation evidence to the TLS session
Updated under an hour ago ()
Does this affect you?
It affects Privasys go. Add what you run to find out whether that includes you.
EPSS puts the chance of exploitation in the next 30 days at 0.12%, higher than 2% of scored CVEs.
Do this next
Free account, 1 product
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.
- CVSS
- 9.1 CRITICAL (v4.0, CNA)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
- Weakness (CWE)
- CWE-346
- Known exploited
- Not in CISA's KEV catalog
- EPSS (exploitation in the next 30 days)
- 0.12% (percentile 2)
- Assigned by
- GitHub_M
- NVD analysis
- Deferred
- Record last updated
- Oct 13, 2026
- First seen by InfoSec Signals
- Oct 9, 2026
Affected products
Privasys go privasys:go (from the name) | before privasys-v0.5.1-go1.26.5 | CNA record |
References
- https://github.com/Privasys/go/security/advisories/GHSA-7jfw-53rm-phh2x-refsource-confirm
- https://github.com/Privasys/go/commit/00a7d21ba53bba0ea09ac7a67eb2c6714e651700x-refsource-misc
- https://github.com/Privasys/go/releases/tag/privasys-v0.5.1-go1.26.5x-refsource-misc
- https://privasys.org/blog/binding-attestation-to-the-tls-sessionx-refsource-misc
The CVE record on cve.org NVD's entry
The CVE record is authoritative. Products marked “from the name” were identified from the CNA's free-text names, not a CPE, and are matched less certainly. This product uses the NVD API but is not endorsed or certified by the NVD.