Google gVisor's runsc component exhibited a local privilege escalation vulnerability due to incorrect handling of file access perm

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

A weak hashing algorithm and small sizes of seeds/secrets in Google's gVisor allowed for a remote attacker to calculate a local IP

A denial of service exists in Gvisor Sandbox where a bug in reference counting code in mount point tracking could lead to a panic,

Google gVisor before 2018-08-22 reuses a pagetable in a different level with the paging-structure cache intact, which allows attac

pkg/sentry/kernel/shm/shm.go in Google gVisor before 2018-11-01 allows attackers to overwrite memory locations in processes runnin

Google gVisor before 2018-08-23, within the seccomp sandbox, permits access to the renameat system call, which allows attackers to