AI Science Tracker

gVisor gofer character-device passthrough permits host-root sandbox escape

Google gVisor · AI involvement attributed to Claude (specific model/version not identified in the CVE credit)

Finding and attribution

On Linux with CUSE enabled, gVisor versions before commit 573a9e73cf844f can pass a container-provided /dev/cuse character device through the gofer to the host. A local attacker with container image deployment privileges can register a host device and use unrestricted CUSE ioctl handling to overwrite root udev helper memory, achieving root code execution on the host.

Product: Google gVisor. AI system: Claude (specific model/version not identified in the CVE credit). Team / organization: Anthropic / Google gVisor maintainers.

CVE identifiers: CVE-2026-96812.

AI and human contribution (source account): Google’s published CVE record credits “Anthropic (using Claude)” as finder for this exact gVisor sandbox-escape issue. The record establishes Claude’s finding role but does not name a model version or describe investigative steps. The same CNA record defines the technical issue and links the gVisor maintainer fix.

Human involvement is only described where the source account establishes it; unknown involvement does not mean none. Vendor confirmation of a flaw does not confirm every claim about AI contribution.

Discovery context: The Google-assigned CVE was published 2026-09-25. The sources do not report exploitation in the wild or establish whether defenders knew of the issue before discovery.

Remediation status: fix documented. The CNA record marks gVisor affected before commit 573a9e73cf844f. The gVisor commit changes special-device open handling, with the default policy dispatching to sentry implementations rather than passing through unsupported character devices to the host. It does not establish deployed patch state.

A source-documented fix does not establish installed patches or current safety. Source checking does not independently reproduce the finding or establish observed exploitation.

Disclosed 25 Sep 2026. AI attribution dated 25 Sep 2026. Sources checked 17 Nov 2026; these are separate dates, not a live installation check.

Recorded CVSS: High · highest recorded score 8.8. Documented technical effects: code execution, privilege escalation.

Severity, consequences and exploitation evidence

Case grouping uses the highest recorded CVSS score, with its version-specific severity band. It is descriptive, not a combined or editorial risk index. All recorded assessments remain below; scores from different versions and sources may disagree. CVSS specifications define version-specific scoring and severity bands.

  • CVE-2026-96812: CVSS 4.0 · 8.8 (High) · vector not available. Google CNA CVE record · checked 17 Nov 2026.

CVE-2026-96812: code execution, privilege escalation.
Prerequisites / affected scope: Linux gVisor with CUSE enabled; attacker must be able to deploy a container image that includes a /dev/cuse character device node. Opening the device passes through to the host, where unrestricted CUSE ioctl handling can overwrite root udev helper memory..
Exploitation evidence: The Google CNA describes host-root code execution as the vulnerability impact; it does not report exploitation in the wild.. Impact source · checked 17 Nov 2026.

Documented fix: The CNA record marks gVisor affected before commit 573a9e73cf844f. The gVisor commit changes special-device open handling, with the default policy dispatching to sentry implementations rather than passing through unsupported character devices to the host. It does not establish deployed patch state.

Original evidence

Download this source record (JSON)

Open this case in the interactive tracker · Browse all static security cases