Skip to main content
CVE-2026-108267VulnerabilityPublished Updated

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

Affects MicrosoftSource GCVE Database

0
Compare
Authoritative record:CVE-2026-108267· Critical 9.1

Not known to be exploited · CVSS 9.1 Critical : upgrade to 0.5.1 as a priority.

Data as of 17 Nov 2026, 10:20 UTC

CVSS 4.0 base score
9.1Critical
How severe the flaw is on the 0–10 CVSS scale.
Patch
Available – fixed in 0.5.1
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

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 9 Oct 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponized: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 16 Nov 2026.

What to do

Upgrade github.com/privasys/go to 0.5.1.

Affected software

ProductAffectedFixed in
PrivasysgoAffected
  • =< privasys-v0.5.1-go1.26.5
Fixed in–
Gogithub.com/privasys/gopkg:golang/github.com/privasys/goOther threatsAffected
  • <0.5.1
Fixed in
  • 0.5.1

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

Description

To determine the support lifecycle for your software, see the Microsoft Support Lifecycle: https://support.microsoft.com/lifecycle

References

Community reviews

Loading reviews…