Gvisor vulnerabilitiesRanked by how likely they are to be used.
Gvisor is made by Google. We track 5 published vulnerabilities in it, across 232 versions. None of them is on the list of flaws known to be exploited today. If you run Gvisor, keep it on a version the vendor still supports.
We keep watching the known-exploited list.
Which Gvisor vulnerabilities are being exploited?
This is the list that matters most: flaws criminals are using now.
None of Gvisor's published vulnerabilities is on the list of flaws known to be exploited today. We keep watching that list.
Which Gvisor flaws are most likely to be used?
Ranked by the latest exploit-likelihood forecast: the chance each flaw is used in an attack in the next 30 days. A high severity score on its own doesn't tell you that. Flaws shared by many other makers' products are left out.
- 0.8%CVE-2018-19333Critical
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,...
- 0.5%CVE-2018-16359Medium
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.
- 0.3%CVE-2018-20168Medium
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...
- 0.2%CVE-2023-7258Medium
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...
- <0.1%CVE-2025-2713High
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.
Running Gvisor? We'll keep checking.
Looking flaws up one at a time doesn't scale. Tell us what you run once, and we tell you which flaws matter to you, in what order, and keep watching for new ones.
- Tell us what you runPick your software from a list, or let us work it out from your website.
- We match it to every flawOver 400,000 published flaws, checked against your list.
- Ranked by real-world riskA 0 to 100 score, led by evidence criminals are using it.
- Told as soon as we knowAn alert by email, in the app or by webhook to your own tools.
Free plan, no card needed. Nothing to install.
1 new flaw affects software Acme tracks
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.
- Matched to
- Gvisor on Acme's software list
- What to do
- Plan in the vendor’s update
Sent to the alert recipients Acme chose. Also in the app and to Acme's webhook.
We track 5 published vulnerabilities listed under the name Gvisor, across 232 versions.
None of Gvisor's vulnerabilities is on the list of flaws known to be exploited today.
Create a EdgeProtect account and track Gvisor. We match it against every published flaw, give each one a risk score from 0 to 100 and keep watching, so you hear about new ones as soon as we know, by email, in the app or by webhook.