CVE Intelligence
Analysis AI-assisted

CVE-2026-108267: Privasys Go RA-TLS Attestation Not Bound to TLS Session

Privasys Go, a Go language fork that adds RA-TLS support, has a flaw in challenge-mode RA-TLS certificates prior to privasys-v0.5.1-go1.26.5. Attestation quotes were bound to the certificate key and client nonce but not to the active TLS session, which allows a genuine quote to be relayed onto another connection. The record assigns a critical severity with CVSS 4.0 score 9.1 and shows no KEV listing.

Published Oct 13, 2026 · Updated Oct 13, 2026 · Ler em português

Overview

Privasys Go is a maintained fork of the Go programming language that adds RA-TLS support to crypto/tls. According to the record, challenge-mode RA-TLS certificates bound the quote ReportData to the certificate public key and client nonce but not to the active TLS session. The weakness is classified as CWE-346 in the record.

Impact

  • An attacker who has obtained an enclave TLS private key could relay a genuine quote onto another connection.
  • A relying party could accept a handshake terminated by the attacker as an attested enclave connection.
  • The GitHub CNA rates the issue critical with CVSS 4.0 score 9.1. The vector in the record indicates high confidentiality and integrity impact and no availability impact.

Affected products and versions

  • The affected product is Privasys Go. The record states the issue exists prior to privasys-v0.5.1-go1.26.5.
  • The record contains no structured affected or fixed version data, so the exact range of impacted versions is unknown from the sources consulted.
  • The fixed release referenced is privasys-v0.5.1-go1.26.5, as shown on the GitHub release page.

Exploitation status

  • The record shows the vulnerability is not listed in the CISA KEV catalog.
  • No confirmed exploitation appears in the sources consulted.
  • The EPSS probability is 0.00117 with percentile 0.01563, dated 2026-10-13, which indicates a low predicted likelihood of exploitation.

Remediation and mitigation

  • Upgrade Privasys Go to privasys-v0.5.1-go1.26.5 or a later release that includes the fix.
  • Review the GitHub security advisory for vendor guidance.
  • If an enclave TLS private key may have been exposed, treat it as compromised, rotate it and the associated certificates after upgrading.
  • Until the fixed version is deployed, relying parties may want to avoid treating RA-TLS attestation alone as proof of the identity of the peer in a given session.

Detection guidance

  • Review RA-TLS handshake logs for unexpected peers or attestations accepted from unfamiliar network paths.
  • Look for attestation evidence that appears on multiple unrelated connections, where the telemetry allows it.
  • Inventory which builds of the Privasys Go fork are deployed in enclave services and in relying party components.

Limitations of the available information

  • The record does not describe the technical details of the fix. The referenced commit was not analyzed for this text.
  • Affected version boundaries, workarounds and deployment figures are not provided in the record.
  • The Privasys blog post is listed as a reference, but its content was not reviewed for this analysis.

Frequently asked questions

What does CVE-2026-108267 affect?

The record identifies Privasys Go, a Go fork with RA-TLS support, for versions prior to privasys-v0.5.1-go1.26.5. The exact list of affected versions is not provided in the record.

Is this vulnerability known to be exploited?

The record shows it is not listed in the CISA KEV catalog and no confirmed exploitation appears in the sources consulted. The EPSS probability is low at 0.00117.

This analysis was drafted with AI assistance from verified source data and automatically checked against it.