Bug 2548422 - CVE-2026-107935 rootlesskit: gvisor-tap-vsock: unathenticated arbitrary file deletion on the host via /expose [fedora-all]
Summary: CVE-2026-107935 rootlesskit: gvisor-tap-vsock: unathenticated arbitrary file ...
Keywords:
Status: CLOSED NOTABUG
Alias: None
Product: Fedora
Classification: Fedora
Component: rootlesskit
Version: rawhide
Hardware: Unspecified
OS: Unspecified
high
high
Target Milestone: ---
Assignee: Gordon Messmer
QA Contact:
URL:
Whiteboard: {"flaws": ["0b2cf099-394f-4202-b210-3...
Depends On:
Blocks: CVE-2026-107935
TreeView+ depends on / blocked
 
Reported: 2026-10-09 08:56 UTC by Cedric Buissart
Modified: 2026-10-14 19:00 UTC (History)
5 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2026-10-14 19:00:13 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)

Description Cedric Buissart 2026-10-09 08:56:54 UTC
Disclaimer: Community trackers are created by Red Hat Product Security team on a best effort basis. Package maintainers are required to ascertain if the flaw indeed affects their package, before starting the update process.

A path-traversal flaw was found in gvproxy (gvisor-tap-vsock) in the port-forwarder's /services/forwarder/expose REST endpoint. When invoked with protocol=unix, the caller-supplied local field was passed without any validation to os.Remove() followed by net.Listen("unix", ...) on the host filesystem. Because this endpoint is exposed unauthenticated on the VM gateway (192.168.127.1:80), a process inside the guest VM — including an unprivileged container — could send a single HTTP POST to delete an arbitrary file owned by the gvproxy user on the host and replace it with a unix-socket inode. This crosses the container/VM-to-host isolation boundary, allowing destruction of sensitive host files (SSH keys, kubeconfig, shell/registry configuration) and denial of service. The issue was fixed by removing the os.Remove() call so pre-existing files can no longer be deleted or overwritten.

Comment 1 Brad Smith 2026-10-14 19:00:13 UTC
Not reported by govulncheck on v3.3.0


Note You need to log in before you can comment on or make changes to this bug.