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.
CVE-2026-108267
CRITICALPre-NVD 9.19.1
EchelonGraph scoreLOW confidence
This critical-severity CVE scores 9.1 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit-prediction score not yet available (the EPSS model rescores nightly; freshly-published CVEs typically appear within 48 hours). GitHub Security Advisory data not yet ingested — confidence will rise once GHSA publishes (typical lag: hours to days for open-source ecosystem CVEs; never for infrastructure-only CVEs).
Triggered by: NVD CVSS baseline
Sources: secondary
9.1EG
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
- High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: —CVSS: 9.1Exploit: None knownExposed services: Not assessed
A fix is available — apply it.
- CVSS v3
- 9.1
- EG Score
- 9.1CRITICALlow confidence
- EG Risk
- 45EG Risk 45/100CISA SSVC
EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).
How it’s computedSeverity91% × 45%Exploitation0% × 40%Automatability30% × 15%CISA SSVC: Track at low or medium mission impact; Track* or Attend at high (mission-essential systems).Action: A fix is available. Apply it within your standard update timelines at low or medium mission impact and sooner than that at high. - EPSS PROB
- —
- EPSS %ILE
- —
- KEV
- Not listed
CISA SSVCTrack at low or medium mission impact; Track* or Attend at high (mission-essential systems).
A fix is available. Apply it within your standard update timelines at low or medium mission impact and sooner than that at high.
Exploitation none (no KEV listing, exploit record or EPSS ≥ 50%) · Automatable unknown (not published for this CVE) · Technical impact total (CVSS ≥ 9.0). Mission impact is CISA's Mission & Well-being decision point, and only you can judge it: high means the affected system is essential to your organisation's mission, or its compromise could cause irreversible harm to people. CISA's decision table
Published
October 9, 2026
Last Modified
October 9, 2026
Advisory Details (4)
Auto-updated Oct 9, 2026Patch available. Sources: github_release, github, github_commit.
generic
Blog | Confidential Computing Is Not Broken: A Calm Look at the RA-TLS Attestation Flaw | Privasys
https://privasys.org/blog/binding-attestation-to-the-tls-sessiongithub_release Patch Available
privasys-v0.5.1-go1.26.5 — RA-TLS challenge-response + session channel binding
Patch available: Privasys/go privasys-v0.5.1-go1.26.5
https://github.com/Privasys/go/releases/tag/privasys-v0.5.1-go1.26.5github_commit Patch Available
commit 00a7d21ba53b (Privasys/go)
Patch available: Privasys/go privasys-v0.5.1-go1.26.5 (contains commit 00a7d21ba53b)
https://github.com/Privasys/go/commit/00a7d21ba53bba0ea09ac7a67eb2c6714e651700githubMentions a patch (unverified)
Privasys Go fork: RA-TLS challenge mode did not bind attestation evidence to the TLS session · Advisory · Privasys/go · GitHub
https://github.com/Privasys/go/security/advisories/GHSA-7jfw-53rm-phh2Weakness Classification(1)
MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.
Data Freshness Timeline
(refreshed 3× in last 7d / 3× in last 30d)
Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.
- 2026-10-09 22:22 UTCEG score recompute
- 2026-10-09 21:25 UTCEG score recompute
- 2026-10-09 21:25 UTCMITRE cvelistV5first tracked
Related CVEs(same CWE)
Frequently asked(4)
What is CVE-2026-108267?
CVE-2026-108267 is a critical vulnerability published on October 9, 2026. 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…
When was CVE-2026-108267 disclosed?
CVE-2026-108267 was first published on October 9, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
What is the CVSS score of CVE-2026-108267?
CVE-2026-108267 has a CVSS base score of 9.1 (a secondary CVSS source that NVD displays; NVD's own analysis pending). The EG score is currently aggregating — additional source signals are being incorporated as they become available..
How do I remediate CVE-2026-108267?
A fix for CVE-2026-108267 is available: update to the fixed version the vendor names in its advisory.
Dependency Blast Radius
Explore the affected products and dependency analysis for CVE-2026-108267
Is Your Infrastructure Affected by CVE-2026-108267?
EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.