CVE-2026-95702

Code Execution in Host Sentry Process via Double Free in gVisor VFS MemoryFile

Published Oct 9, 2026 CVSS 4.0 · 8.5 High EPSS < 1% KEV · Not listed
Description
Use-after-free vulnerability in VFS in Google gVisor prior to release 20260831.0 on all platforms allows a local attacker with standard container privileges to achieve code execution in the host sentry process by double-freeing the backing MemoryFile from an in-sandbox overlay filesystem. The sentry process remains confined by host-level Linux seccomp and namespace boundaries.

Analysis

AI-generated

Technical impact

The bug is a double‑free and use‑after‑free condition in gVisor’s virtual filesystem layer that allows a process running inside a container to free a MemoryFile backing object twice and then trigger a use‑after‑free that ends up executing code inside the host’s sentry process. Because the sentry is confined only by host‑level seccomp and namespace isolation, a successful exploitation results in local code execution on the host that can be leveraged for further privilege escalation. This defect is classified as CWE‑415, CWE‑416, and CWE‑825.

Affected Systems

Google gVisor on all platforms is affected; any installation that has not been updated to release 20260831.0 or later is vulnerable. The issue appears in every component that exposes the VFS overlay filesystem to user containers.

Risk and Exploitability

The CVSS base score of 8.5 reflects a high severity for local privilege escalation. The EPSS score of 0.00084 indicates a very low probability of exploitation, and the vulnerability is not listed in CISA’s KEV catalog. The attack vector is local and requires a container to have standard privileges to manipulate the filesystem within the sandbox. An attacker would need to run a malicious program inside the container to trigger the double‑free, after which arbitrary code can execute in the host sentry process. Given the EPSS score of 0.00084, the focus should be on patching and hardening container boundaries.

Remediation

No solution or workaround provided in the CVE record.

OpenCVE Recommended Actions

  • Upgrade Google gVisor to release 20260831.0 or later to remove the double‑free bug.
  • Remove unnecessary privileges from containers; run them with the least privileged user accounts and avoid giving them root access to the overlay filesystem.
  • Configure the host to enforce seccomp profiles and namespace isolation for sentry processes, ensuring that even if code runs inside the sentry low‑privileged state, it cannot escape to the broader system.

Generated by OpenCVE AI on October 13, 2026 at 02:10 UTC.

Tracking

Sign in to view the affected projects.

Advisories

No advisories available
History
Type Values Removed Values Added
Metrics ssvc

{'options': {'Automatable': 'no', 'Exploitation': 'none', 'Technical Impact': 'total'}, 'version': '2.0.3'}

Type Values Removed Values Added
Weaknesses CWE-825
References
Metrics threat_severity

None

cvssV3_1

{'score': 7.8, 'vector': 'CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H'}

threat_severity

Important

Type Values Removed Values Added
First Time appeared Google
Google gvisor
Vendors & Products Google
Google gvisor
Type Values Removed Values Added
Description Use-after-free vulnerability in VFS in Google gVisor prior to release 20260831.0 on all platforms allows a local attacker with standard container privileges to achieve code execution in the host sentry process by double-freeing the backing MemoryFile from an in-sandbox overlay filesystem. The sentry process remains confined by host-level Linux seccomp and namespace boundaries.
Title Code Execution in Host Sentry Process via Double Free in gVisor VFS MemoryFile
Weaknesses CWE-415
CWE-416
References
Metrics cvssV4_0

{'score': 8.5, 'vector': 'CVSS:4.0/AV:L/AC:L/AT:N/PR:L/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N'}

Weaknesses

Sources

Status
PUBLISHED
Assigner
Google
Published
Updated
Oct 15, 2026, 6:15 PM
Reserved
Sep 22, 2026, 2:46 PM
Status
Awaiting Analysis
Published
Oct 9, 2026, 3:17 PM
Modified
Oct 15, 2026, 7:17 PM
Severity
Important
Public date
Oct 9, 2026, 2:44 PM