Gvisor (Google) - vulnerabilities (CVEs)
7 CVEs, 1 in the last 30 days, 234 known versions, newest CVE from 2026-10-09. Vendor: Google.
CVEs of Gvisor
- CVE-2026-95702 - CVSS 8.5 (high), 2026-10-09: 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…
- CVE-2026-96812 - CVSS 8.8 (high), 2026-09-25: 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…
- CVE-2025-2713 - CVSS 7.8 (high), 2025-03-28: Google gVisor's runsc component exhibited a local privilege escalation vulnerability due to incorrect handling of file access permissions, which allowed…
- CVE-2024-10603 - CVSS 6.3 (medium), 2025-01-30: 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…
- CVE-2024-10026 - CVSS 6.3 (medium), 2025-01-30: 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…
- CVE-2023-7258 - CVSS 6.5 (medium), 2024-05-15: 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…
- CVE-2018-20168 - CVSS 5.5 (medium), 2018-12-17: 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…
- CVE-2018-19333 - CVSS 9.8 (critical), 2018-11-17: 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…
- CVE-2018-16359 - CVSS 6.8 (medium), 2018-09-02: 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.
