Bug 2482487 (CVE-2026-9804) - CVE-2026-9804 kubevirt: kubevirt: VMExport directory symlink escape enables exporter pod file read
Summary: CVE-2026-9804 kubevirt: kubevirt: VMExport directory symlink escape enables e...
Keywords:
Status: NEW
Alias: CVE-2026-9804
Product: Security Response
Classification: Other
Component: vulnerability
Version: unspecified
Hardware: All
OS: Linux
high
high
Target Milestone: ---
Assignee: Product Security DevOps Team
QA Contact:
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2026-05-28 06:11 UTC by OSIDB Bzimport
Modified: 2026-05-28 08:08 UTC (History)
5 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed:
Embargoed:


Attachments (Terms of Use)

Description OSIDB Bzimport 2026-05-28 06:11:41 UTC
A path traversal vulnerability was found in KubeVirt's virt-exportserver component. The VMExport directory endpoint uses Go's http.FileServer(http.Dir(mountPoint)) to serve filesystem PVC contents. Because http.Dir follows symbolic links, an attacker who can control files inside an exported filesystem PVC can place a symlink pointing outside the PVC mount root and read arbitrary files from the exporter pod's filesystem through the VMExport directory endpoint.

This vulnerability affects filesystem PVCs that do not have the cdi.kubevirt.io/storage.contentType annotation set to a KubeVirt content type. PVCs with KubeVirt content type receive raw/gzip export endpoints instead of the vulnerable directory endpoint. Namespaces with mixed workloads (pods and VMs) are more likely to have affected PVCs than namespaces hosting only KubeVirt VMs.

To exploit this vulnerability, an attacker must have namespace-level access sufficient to create or control the contents of a filesystem PVC, create a VirtualMachineExport resource for that PVC, and possess or obtain the VMExport token.


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