Google gVisor vulnerabilities

Latest Google gVisor CVEs

Newest publication first

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

   Published 2026-10-09

   High·CVSS 8.5 EPSS 0.08%

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

2. CVE-2026-96812 Host Root Sandbox Escape in gVisor via Character Device Passthrough and CUSE

   Published 2026-09-25

   High·CVSS 8.8 EPSS 0.13%

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

3. CVE-2025-2713 Improper File Permission Handling in Google gVisor runsc

   Published 2025-03-28

   Medium·CVSS 6.8 EPSS 0.07%

   Google gVisor's runsc component exhibited a local privilege escalation vulnerability due to incorrect handling of file access permissions, which allowed unprivileged users to access restricted files. This occurred because the process initially ran with root-like permissions until...

4. CVE-2024-10603 Weaknesses in the generation of TCP/UDP source ports and some other header values in Google's gVisor allowed them to be predicted by an external attacker in some circumstances.

   Published 2025-01-30

   Medium·CVSS 6.3 EPSS 0.27%

   Weaknesses in the generation of TCP/UDP source ports and some other header values in Google's gVisor allowed them to be predicted by an external attacker in some circumstances.

5. CVE-2024-10026 Improved Seeding and Hashing In gVisor

   Published 2025-01-30

   Medium·CVSS 6.3 EPSS 0.23%

   A weak hashing algorithm and small sizes of seeds/secrets in Google's gVisor allowed for a remote attacker to calculate a local IP address and a per-boot identifier that could aid in tracking of a device in certain circumstances.

6. CVE-2023-7258 Denial-of-Service in Gvisor

   Published 2024-05-15

   Medium·CVSS 6.5 EPSS 0.17%

   A denial of service exists in Gvisor Sandbox where a bug in reference counting code in mount point tracking could lead to a panic, making it possible for an attacker running as root and with permission to mount volumes to kill the sandbox. We recommend upgrading past commit 6a112...

7. CVE-2018-20168 Google gVisor before 2018-08-22 reuses a pagetable in a different level with the paging-structure cache intact, which allows attackers to cause a denial of service ("physical address not valid" panic)...

   Published 2018-12-17

   Medium·CVSS 5.5 EPSS 0.28%

   Google gVisor before 2018-08-22 reuses a pagetable in a different level with the paging-structure cache intact, which allows attackers to cause a denial of service ("physical address not valid" panic) via a crafted application.

8. CVE-2018-19333 pkg/sentry/kernel/shm/shm.go in Google gVisor before 2018-11-01 allows attackers to overwrite memory locations in processes running as root (but not escape the sandbox) via vectors involving IPC_RMID....

   Published 2018-11-17

   Critical·CVSS 9.8 EPSS 0.81%

   pkg/sentry/kernel/shm/shm.go in Google gVisor before 2018-11-01 allows attackers to overwrite memory locations in processes running as root (but not escape the sandbox) via vectors involving IPC_RMID shmctl calls, because reference counting is mishandled.

9. CVE-2018-16359 Google gVisor before 2018-08-23, within the seccomp sandbox, permits access to the renameat system call, which allows attackers to rename files on the host OS.

   Published 2018-09-02

   Medium·CVSS 6.8 EPSS 0.45%

   Google gVisor before 2018-08-23, within the seccomp sandbox, permits access to the renameat system call, which allows attackers to rename files on the host OS.

Sources: CVE.org, NVD, CISA KEV, FIRST EPSS, OSV and public exploit-reference metadata. Product matching comes from the published CVE records. A proof-of-concept means public code exists; it is not evidence of exploitation.