Skip to content
Threat Brief

← All advisories

CVE-2026-108267

Critical 9.1No known exploitationFix available

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

Record last updated

CVSS score

9.1

Critical on a 0 to 10 scale

EPSS, chance of exploitation in 30 days

0.1%

Higher than 2% of scored CVEs. A prediction, not evidence.

CISA remediation deadline

None

Not in the KEV catalog

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

Patching and mitigation

Patch status
Fix available (source: Microsoft MSRC)
Fix documented (source date)
Mitigation
None documented
Vendor guidance
msrc.microsoft.com (opens in a new tab)

Affected products

VendorProductAffected versionsFixed inPer
Microsoftazl3 gcc 13.2.0-7 on Azure Linux 3.0Not documentedNot documentedMicrosoft MSRC
Microsoftazl3 golang 1.26.7-1 on Azure Linux 3.0Not documentedNot documentedMicrosoft MSRC
Microsoftazl3 golang 1.27.1-1 on Azure Linux 3.0Not documentedNot documentedMicrosoft MSRC
Microsoftazl3 python-tensorboard 2.16.2-6 on Azure Linux 3.0Not documentedNot documentedMicrosoft MSRC
Microsoftazl3 tensorflow 2.16.1-11 on Azure Linux 3.0Not documentedNot documentedMicrosoft MSRC
Privasysgo< privasys-v0.5.1-go1.26.5Not documentedCVE Program

Timeline

  1. Disclosure

    CVE record published by GitHub_M

    Source: CVE Program (opens in a new tab)

  2. Advisory

    Microsoft advisory published

    Source: Microsoft MSRC (opens in a new tab)

  3. Patch

    Fix documented by Microsoft MSRC

    Source: Microsoft MSRC (opens in a new tab)

Vendor guidance and references