Read the docs
TI-2026-70300 Aliases CVE-2026-108267

Privasys Go RA-TLS attestation not bound to the TLS session

Priority MEDIUM 40CWE-346Published · Updated

Key facts

Attack vector
Network
Privileges required
None
User interaction
None
Attack complexity
High
Attack requirements
Present
Impact type
Security bypass
Confidentiality · integrity · availability
High · High · None
Fix status
No fix listed

Attack profile from CVSS 4.0 · CNA. Fix status from CNA. Impact type from CWE-346.

Summary

Privasys Go, a maintained fork of the Go programming language that adds RA-TLS support to crypto/tls, is affected before privasys-v0.5.1-go1.26.5. Challenge-mode RA-TLS certificates bind attestation quote data to the certificate public key and client nonce but not to the active TLS session, an origin validation error (CWE-346). An attacker who holds an enclave TLS private key can relay a genuine quote onto another connection, so a relying party accepts a handshake the attacker terminates as an attested enclave connection.

Written with Claude Haiku 5.5 from the sources below · 2026-10-29

Description from the CNA

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.

Why it matters now

Exploitation None reported CISA SSVC · not in CISA KEV
EPSS 0.00117 1st percentileScored 2026-11-07
Fix No fix listed No fixed version in the sources yet

SSVC decision points

CISA ADP · SSVC 2.0.3

Exploitation
None
Automatable
No
Technical impact
Total

The decision (Track, Attend, Act) also depends on your mission and well-being impact; see CISA's SSVC guide.

Affected products

VendorProductAffected versionsFixed inStatusSource
Privasysgo< privasys-v0.5.1-go1.26.5—No fix listedCNA
  • go VendorPrivasys Affected < privasys-v0.5.1-go1.26.5 Fixed in — No fix listed CNA

Remediation

Upgrade Privasys Go to privasys-v0.5.1-go1.26.5, which fixes this issue.

Written with Claude Haiku 5.5 from the sources below · 2026-10-29

Timeline

  1. 2026-10-10 Threatist record created from CVE-2026-108267
  2. 2026-10-11 Priority changed: MEDIUM → LOW
  3. 2026-10-13 CISA SSVC decision points changed
  4. 2026-10-13 Priority changed: LOW → MEDIUM

References

Other 4

  • TI-2026-70299 Privasys rustls RA-TLS attestation not bound to the TLS session CVSS 4.0CRITICAL 9.1
  • TI-2026-71258 Privasys attested TLS accepts evidence from other TEE platforms CVSS 4.0CRITICAL 9.1
  • TI-2026-70301 Privasys enclave-os-virtual RA-TLS quotes not bound to TLS session CVSS 4.0CRITICAL 9.1
  • TI-2026-70298 enclave-os-mini RA-TLS certificates not bound to TLS session CVSS 4.0CRITICAL 9.1
  • TI-2026-70302 RA-TLS challenge verifier in ra-tls-clients accepts relayed quotes CVSS 4.0CRITICAL 9.1
  • TI-2026-71257 Privasys ra-tls-clients trusts stale attestation after TLS setup CVSS 4.0HIGH 7.2

Sources

This product uses the NVD API but is not endorsed or certified by the NVD. Sources and licences