CVE-2026-108267

CRITICALPre-NVD 9.19.1
EchelonGraph scoreMEDIUM confidence

“—” beside the score: it is equal to the CVSS score beside it.

This critical-severity CVE scores 9.1 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit probability: 0.1% (1st percentile of EPSS-scored CVEs). No GitHub Security Advisory CVSS is on record for this CVE.

Triggered by: Headline CVSS from a secondary CVSS source
Sources: EPSS, a secondary CVSS source
Trending — 3 sources updated this week

Also known asEUVD-2026-96017 (ENISA EUVD)Source: ENISA EUVD

9.1EG
EchelonGraph verdictPlan a fixRemediate within your standard update timelines (the SSVC decision on this page).
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0.1%CVSS: 9.1Exploit: None knownExposed services: Not assessed

A fix is available — apply it.

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.

CVSS v3
9.1
EG Score
9.1CRITICALmedium confidence
EG Risk
41
EG Risk 41/100

EG Risk is EchelonGraph's 0–100 priority score. It fuses impact severity (EG Severity, the CVSS base score, never the KEV-floored or EPSS-lifted EG Score) with real-world exploitation and automatability, under weights EchelonGraph set by hand, so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner.

How it’s computed (value × EchelonGraph’s weight)
Severity91% × 45%
Impact severity (EG Severity): CVSS 9.1 of 10. Never the KEV-floored or EPSS-lifted EG Score.
Exploitation0.1% × 40%
FIRST EPSS: the 30-day exploitation probability when EchelonGraph scored this CVE.
Automatability0% × 15%
CISA's SSVC Automatable value: no (Vulnrichment).
SSVC (CISA's decision table, applied by EchelonGraph): Track at low or medium mission impact; Track* at high (mission-essential systems).
Exploitation none (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact total (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE.
Action: A fix is available. Apply it within your standard update timelines.
EPSS PROB
0.1%
EPSS %ILE
1st
KEV
Not listed

What the EG score is made of (scorer v4.0: the three questions the 0–10 score mixes, published apart · methodology)

The EG score (9.1): severity, escalated by confirmed exploitation. This CVE's 9.1 is its impact severity (EG Severity), not escalated.

EG Severity
9.1 CRITICALCVSS-B, impact only: no KEV listing, EPSS or EG-KEV tier raises it.a secondary CVSS source · CVSS v3.0 or v3.1
EG Likelihood
0.1% within 30 daysSource: FIRST EPSS (model v2026.06.15, score date 2026-11-01). FIRST's exploitation probability, not an EchelonGraph model.
Confirmed exploitation
None on record (CISA KEV, EG-KEV Tier 1)Reported apart from the likelihood: an observed fact, not a probability.
EG Priority
SSVC Track at medium mission impactTrack at low or medium mission impact; Track* at high (mission-essential systems).CISA BOD 26-04: 14 days if the affected system is publicly exposed; Fix on system upgrade if it is not.Each input and its source, and whom BOD 26-04 binds: the SSVC and BOD 26-04 blocks below.

SSVC (CISA's decision table, applied by EchelonGraph)Track at low or medium mission impact; Track* at high (mission-essential systems).

A fix is available. Apply it within your standard update timelines.

Exploitation none (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact total (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE. Mission impact is CISA's Mission & Well-being decision point, and only you can judge it. CISA's table makes it high when Mission Prevalence is Essential — the vulnerable component "directly provides capabilities that constitute at least one MEF for at least one entity" (MEF: mission essential function) — or when Public Well-Being Impact is Irreversible: "multiple fatalities are likely", the cyber-physical system "is likely lost or destroyed", "extreme or serious externalities" are imposed on other parties, or social systems such as elections or the financial grid "are destabilized and potentially collapse". CISA's decision table

BOD 26-04 (CISA's remediation timeline, Table 1)14 days if the affected system is publicly exposed; Fix on system upgrade if it is not.

The score's inputs: In CISA KEV no (CISA's KEV catalog) · Automatable no (CISA Vulnrichment) · Technical impact total (CISA Vulnrichment). Whether your system is publicly exposed is yours to answer. BOD 26-04 binds US Federal Civilian Executive Branch agencies; for anyone else it is CISA's published timeline, a reference rather than an obligation. The directive · how EchelonGraph applies it

Published

October 9, 2026

Last Modified

October 16, 2026

Advisory Details (4)

Auto-updated Oct 9, 2026
Patch available. Sources: github_release, github, github_commit.
Web page

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-session
GitHub 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.5
GitHub 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/00a7d21ba53bba0ea09ac7a67eb2c6714e651700
GitHub advisoryMentions 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-phh2

Vendor Advisories for CVE-2026-108267(1)

These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.

Weakness Classification(1)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Data Freshness Timeline

(refreshed 17× in last 7d / 63× in last 30d)

Each row is a time one of our pipelines fetched, updated or re-scored this CVE. 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. An arrow marks a change the record states ("CVSS v3 → 9.1"); EPSS and GHSA rows show the values recorded at that time, not what changed (EPSS values are rounded; hover one for the exact figures). Most recent first.

  1. 2026-11-01 19:16 UTCEG score recompute
  2. 2026-11-01 19:16 UTCVendor advisory
  3. 2026-11-01 16:33 UTCEPSS rescoreEPSS 0.1% · 1st percentile
  4. 2026-10-31 18:04 UTCEG score recompute
  5. 2026-10-31 18:04 UTCVendor advisory
  6. 2026-10-31 16:31 UTCEPSS rescoreEPSS 0.1% · 1st percentile
  7. 2026-10-30 16:52 UTCEG score recompute
  8. 2026-10-30 16:52 UTCVendor advisory
  9. 2026-10-29 16:32 UTCEPSS rescoreEPSS 0.1% · 1st percentile
  10. 2026-10-29 15:42 UTCEG score recompute
  11. 2026-10-29 15:42 UTCVendor advisory
  12. 2026-10-28 16:31 UTCEPSS rescoreEPSS 0.1% · 1st percentile
  13. 2026-10-28 14:19 UTCEG score recompute
  14. 2026-10-28 14:19 UTCVendor advisory
  15. 2026-10-27 16:31 UTCEPSS rescoreEPSS 0.1% · 1st percentile
  16. 2026-10-27 04:43 UTCEG score recompute
  17. 2026-10-26 16:30 UTCEPSS rescoreEPSS 0.1% · 1st percentile
  18. 2026-10-25 23:06 UTCEG score recompute
  19. 2026-10-25 23:06 UTCVendor advisory
  20. 2026-10-25 16:32 UTCEPSS rescoreEPSS 0.1% · 1st percentile
  21. 2026-10-25 14:54 UTCEG score recompute
  22. 2026-10-24 21:55 UTCEG score recompute
  23. 2026-10-24 21:55 UTCVendor advisory
  24. 2026-10-23 20:44 UTCEG score recompute
  25. 2026-10-23 16:31 UTCEPSS rescoreEPSS 0.1% · 1st percentile
Show 38 more
  1. 2026-10-22 19:34 UTCEG score recompute
  2. 2026-10-21 18:22 UTCEG score recompute
  3. 2026-10-21 18:22 UTCVendor advisory
  4. 2026-10-21 16:32 UTCEPSS rescoreEPSS 0.1% · 1st percentile
  5. 2026-10-20 17:10 UTCEG score recompute
  6. 2026-10-20 16:32 UTCEPSS rescoreEPSS 0.1% · 1st percentile
  7. 2026-10-19 23:44 UTCEG score recompute
  8. 2026-10-19 23:44 UTCVendor advisory
  9. 2026-10-19 16:31 UTCEPSS rescoreEPSS 0.1% · 1st percentile
  10. 2026-10-18 22:31 UTCEG score recompute
  11. 2026-10-18 22:31 UTCVendor advisory
  12. 2026-10-18 16:31 UTCEPSS rescoreEPSS 0.1% · 1st percentile
  13. 2026-10-18 05:07 UTCEG score recompute
  14. 2026-10-17 21:19 UTCEG score recompute
  15. 2026-10-17 21:19 UTCVendor advisory
  16. 2026-10-17 16:33 UTCEPSS rescoreEPSS 0.1% · 1st percentile
  17. 2026-10-16 20:06 UTCEG score recompute
  18. 2026-10-16 16:40 UTCEPSS rescoreEPSS 0.1% · 1st percentile
  19. 2026-10-16 01:11 UTCEG score recompute
  20. 2026-10-15 16:31 UTCEPSS rescoreEPSS 0.1% · 1st percentile
  21. 2026-10-14 20:17 UTCEG score recompute
  22. 2026-10-14 16:32 UTCEPSS rescoreEPSS 0.1% · 1st percentile
  23. 2026-10-13 16:33 UTCEPSS rescoreEPSS 0.1% · 1st percentile
  24. 2026-10-13 16:26 UTCEG score recompute
  25. 2026-10-13 16:26 UTCVendor advisory
  26. 2026-10-13 16:01 UTCEG score recompute
  27. 2026-10-13 16:01 UTCVendor advisory
  28. 2026-10-12 16:38 UTCEG score recompute
  29. 2026-10-12 16:33 UTCEPSS rescoreEPSS 0.1% · 1st percentile
  30. 2026-10-11 19:31 UTCEG score recompute
  31. 2026-10-11 18:26 UTCEG score recompute
  32. 2026-10-11 14:59 UTCEG score recompute
  33. 2026-10-11 11:20 UTCEG score recompute
  34. 2026-10-10 22:59 UTCEG score recompute
  35. 2026-10-10 19:59 UTCEPSS rescoreEPSS 0.1% · 1st percentile
  36. 2026-10-09 22:22 UTCEG score recompute
  37. 2026-10-09 21:25 UTCEG score recomputeFirst assessed: 9.1 CRITICAL
  38. 2026-10-09 21:25 UTCMITRE cvelistV5first tracked

Related CVEs(same CWE)

Frequently asked(5)

What is CVE-2026-108267?
CVE-2026-108267 is a critical-severity vulnerability; its CVE record was 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 the CVE record for CVE-2026-108267 published?
The CVE record for CVE-2026-108267 was published on October 9, 2026. That is the record's publication date; the vulnerability itself may have been made public earlier. EchelonGraph's copy of the record carries a last-modified date of October 16, 2026; the record at its source may have been updated since.
Is CVE-2026-108267 actively exploited?
CVE-2026-108267 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.1% probability of exploitation in the next 30 days (1st percentile of EPSS-scored CVEs).
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).
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. The vendor advisories EchelonGraph has for CVE-2026-108267 are linked in the Vendor Advisories panel on this page.

Dependency Blast Radius

Explore the affected products and dependency analysis for CVE-2026-108267

Explore →

Is Your Infrastructure Affected by CVE-2026-108267?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.

Book a Demo →Browse All CVEs