CVE-2026-96812

HIGHPre-NVD 8.88.8—
EchelonGraph scoreMEDIUM confidence

This high-severity CVE scores 8.8 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit probability: <0.1% (below the 1st percentile of EPSS-scored CVEs). 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: epss, secondary
Trending — 3 sources updated this week
8.8EG
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: <0.1%CVSS: 8.8Exploit: None knownExposed services: Not assessed

A fix is available — apply it.

Improper Exposure of Resource to Wrong Sphere in the host file helper (gofer) in Google gVisor prior to commit 573a9e73cf844f on Linux platforms with CUSE enabled allows a local attacker with container image deployment privileges to achieve root code execution on the host system. By including a /dev/cuse character device node in a container image, opening the device passes through to the host, allowing the sandboxed attacker to register a host device and exploit CUSE unrestricted ioctl handling to overwrite root udev helper memory.

CVSS v3
8.8
EG Score
8.8HIGHmedium confidence
EG Risk
40
EG Risk 40/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 computed
Severity88% × 45%
Exploitation0% × 40%
Automatability0% × 15%
CISA SSVC: Track at low or medium mission impact; Track* at high (mission-essential systems).
Action: A fix is available. Apply it within your standard update timelines.
EPSS PROB
<0.1%
EPSS %ILE
below the 1st
KEV
Not listed

CISA SSVCTrack 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). 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

September 25, 2026

Last Modified

September 25, 2026

Advisory Details (1)

Auto-updated Sep 25, 2026
Patch available. Sources: github_commit.
github_commit Patch Available

commit 573a9e73cf84 (google/gvisor)

Patch available: google/gvisor release-20260831.0 (contains commit 573a9e73cf84)

https://github.com/google/gvisor/commit/573a9e73cf844f

Vendor Advisories for CVE-2026-96812(1)

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

Weakness Classification(2)

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

Data Freshness Timeline

(refreshed 26× in last 7d / 39× 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.

  1. 2026-10-05 08:20 UTCGHSA enrichment
  2. 2026-10-04 19:32 UTCGHSA enrichment
  3. 2026-10-04 06:43 UTCGHSA enrichment
  4. 2026-10-03 17:55 UTCEG score recompute
  5. 2026-10-03 17:55 UTCGHSA enrichment
  6. 2026-10-03 14:26 UTCEPSS rescore
  7. 2026-10-03 05:06 UTCGHSA enrichment
  8. 2026-10-02 16:17 UTCGHSA enrichment
  9. 2026-10-02 16:17 UTCGHSA enrichment
  10. 2026-10-02 16:17 UTCGHSA enrichment
  11. 2026-10-02 03:28 UTCEG score recompute
  12. 2026-10-02 03:28 UTCGHSA enrichment
  13. 2026-10-01 19:51 UTCEPSS rescore
  14. 2026-10-01 14:40 UTCGHSA enrichment
  15. 2026-10-01 01:52 UTCEG score recompute
  16. 2026-10-01 01:52 UTCGHSA enrichment
  17. 2026-09-30 15:04 UTCEPSS rescore
  18. 2026-09-30 13:04 UTCGHSA enrichment
  19. 2026-09-30 00:14 UTCEG score recompute
  20. 2026-09-30 00:14 UTCGHSA enrichment
  21. 2026-09-29 11:25 UTCGHSA enrichment
  22. 2026-09-28 22:37 UTCEG score recompute
  23. 2026-09-28 22:37 UTCGHSA enrichment
  24. 2026-09-28 13:52 UTCEPSS rescore
  25. 2026-09-28 13:52 UTCEPSS rescore
Show 14 more
  1. 2026-09-28 09:49 UTCGHSA enrichment
  2. 2026-09-27 21:01 UTCGHSA enrichment
  3. 2026-09-27 08:12 UTCGHSA enrichment
  4. 2026-09-26 19:23 UTCEG score recompute
  5. 2026-09-26 19:23 UTCGHSA enrichment
  6. 2026-09-26 15:59 UTCEPSS rescore
  7. 2026-09-26 06:34 UTCGHSA enrichment
  8. 2026-09-25 17:44 UTCEG score recompute
  9. 2026-09-25 17:44 UTCGHSA enrichment
  10. 2026-09-25 16:24 UTCEG score recompute
  11. 2026-09-25 16:24 UTCGHSA enrichment
  12. 2026-09-25 15:24 UTCEG score recompute
  13. 2026-09-25 14:54 UTCEG score recompute
  14. 2026-09-25 14:54 UTCMITRE cvelistV5first tracked

Related CVEs(same CWE)

Frequently asked(5)

What is CVE-2026-96812?
CVE-2026-96812 is a high vulnerability published on September 25, 2026. Improper Exposure of Resource to Wrong Sphere in the host file helper (gofer) in Google gVisor prior to commit 573a9e73cf844f on Linux platforms with CUSE enabled allows a local attacker with container image deployment privileges to achieve root code execution on the host system. By including a…
When was CVE-2026-96812 disclosed?
CVE-2026-96812 was first published on September 25, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-96812 actively exploited?
CVE-2026-96812 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a <0.1% probability of exploitation in the next 30 days (below the 1st percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-96812?
CVE-2026-96812 has a CVSS base score of 8.8 (a secondary CVSS source that NVD displays; NVD's own analysis pending).
How do I remediate CVE-2026-96812?
A fix for CVE-2026-96812 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2026-96812 are linked in the Vendor Advisories panel on this page.

Dependency Blast Radius

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

Explore →

Is Your Infrastructure Affected by CVE-2026-96812?

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

Book a Demo →Browse All CVEs