# CVE-2026-95702: Code Execution in Host Sentry Process via Double Free in gVisor VFS MemoryFile

> A local attacker in a container can achieve code execution in the host sentry process via a double-free vulnerability in gVisor's VFS MemoryFile.

- **Severity:** High 8.5 (`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`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 9 Oct 2026
- **Updated:** 15 Oct 2026
- **Also known as:** DEBIAN-CVE-2026-95702, GHSA-hv4v-f9v2-r8c2, UBUNTU-CVE-2026-95702

## What is CVE-2026-95702?

CVE-2026-95702 is a high-severity use after free vulnerability in Google gVisor, published on 9 Oct 2026. It can only be exploited from the same machine or local network, with no action from the victim.

### Official 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.

Weakness: CWE-416 (Use After Free), CWE-415 (Double Free)

## Which versions are affected by CVE-2026-95702?


## How do I fix CVE-2026-95702?

No fix has been published for CVE-2026-95702 yet. Limit exposure of the affected software until one is available.

## Is CVE-2026-95702 being exploited?

There is no known exploitation of CVE-2026-95702 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-95702 and fix it if it is affected.

What it is: CVE-2026-95702 is a high-severity use after free vulnerability in Google gVisor, published on 9 Oct 2026. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-95702 in the wild and no public exploit code.

Affected product: Google gVisor. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-95702/ (Markdown: https://insights.sbomify.com/CVE-2026-95702/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-95702
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-95702
- OSV: https://osv.dev/vulnerability/CVE-2026-95702

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-95702/
Summaries are generated and may contain mistakes; the official description above is the record.