Medium severity · published Sep 2, 2018
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
6.8
CVSS
0.5%
EPSS
No
On KEV
Description
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.
CVSS vector
CVSS:3.0/AV:N/AC:H/PR:N/UI:N/S:C/C:N/I:H/A:N
Attack vector
Network
Complexity
High
Privileges
None
User interaction
None
Confidentiality
None
Integrity
High
Availability
None
Scope
Changed
Exploitation
Is it being used?
Exploit prediction (EPSS)0.5% · higher than 39% of CVEs
Exploited in the wildNo evidence yet
CISA KEVNot listed
Ransomware campaign useNot known
Affected products
Which versions
GV
Gvisor · Google
before 2018-08-23 · source: NVD
References
NVD
https://nvd.nist.gov/vuln/detail/CVE-2018-16359
CVE.org
https://www.cve.org/CVERecord?id=CVE-2018-16359
Vendor Advisory
https://bugs.chromium.org/p/project-zero/issues/detail?id=1632
Third Party Advisory
https://github.com/google/gvisor/commit/001a4c2493b13a43d62c7511fb509a959ae4abc2
More from Gvisor
9.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…
8.8
CVE-2026-96812
Host Root Sandbox Escape in gVisor via Character Device Passthrough and CUSE
8.5
CVE-2026-95702
Code Execution in Host Sentry Process via Double Free in gVisor VFS MemoryFile
7.8
CVE-2025-2713
Google gVisor's runsc component exhibited a local privilege escalation vulnerability due to incorrect handling of file access permissions, which allowed unprivileged users to…
6.5
CVE-2023-7258
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…