CVE-2026-9804: KubeVirt virt-exportserver Path Traversal Information Disclosure

Technical summary

CVE-2026-9804 is a path traversal vulnerability in KubeVirt's virt-exportserver component affecting the VMExport directory endpoint. The vulnerability exists because the component does not properly validate symlink targets during filesystem export operations. An attacker with Kubernetes namespace-level permissions can craft a Persistent Volume Claim (PVC) containing a symbolic link that traverses outside the mount root. When the exporter processes this PVC, it follows the symlink and exposes files that should remain inaccessible, resulting in unauthorized information disclosure. The root cause is insufficient path canonicalization and symlink resolution checks before serving exported content.

Business impact

Compromise of this vulnerability enables lateral data exfiltration within Kubernetes environments. Attackers can extract sensitive application data, database credentials, API keys, or configuration secrets stored on exporter pods. For organizations using KubeVirt for virtualization workloads, this represents a meaningful risk to data confidentiality. The attack requires prior namespace access, limiting exposure to insider threats or compromised service accounts, but the consequences—unauthorized access to pod filesystem secrets—can be severe in multi-tenant or shared cluster scenarios.

Affected systems

The vulnerability affects KubeVirt deployments where the virt-exportserver component is deployed and used for VM export operations. Specifically, systems using VMExport functionality with Persistent Volume Claims are at risk. The vulnerability requires the attacker to have Kubernetes namespace-level access, indicating exposure is primarily to authenticated users or compromised workloads within the cluster. Organizations running older versions of KubeVirt without a confirmed patched version are vulnerable.

Exploitability

Exploitation requires authentication and namespace-level access within a Kubernetes cluster, which significantly reduces opportunistic attack surface. However, the technical barrier to exploitation is low: an attacker need only create or modify a PVC with a crafted symbolic link and trigger an export operation. The attack is deterministic and does not require timing manipulation or user interaction. For insider threats, disgruntled developers, or operators of compromised workloads sharing a namespace, exploitation is straightforward. The vulnerability is not currently listed in the CISA Known Exploited Vulnerabilities (KEV) catalog.

Remediation

Apply vendor patches to KubeVirt as they become available. Verify the patched version against the official KubeVirt release notes and security advisories. In the interim, implement strict Kubernetes RBAC policies to restrict namespace-level permissions and limit which service accounts can create or modify PVCs used with VMExport. Audit existing PVCs for suspicious symbolic links and monitor virt-exportserver logs for path traversal attempts. Consider disabling VMExport functionality if not actively used in your environment.

Patch guidance

Consult the official KubeVirt security advisories and release notes for confirmed patch versions addressing CVE-2026-9804. Apply patches according to your change management process, testing in non-production environments first. The vulnerability was last modified on 2026-06-30, so vendors should have released updates by or shortly after that date. Prioritize patching systems where VMExport is actively used or exposed to untrusted namespace tenants.

Detection guidance

Monitor virt-exportserver pod logs and container runtime for errors related to symlink resolution or path traversal attempts. Track VMExport API calls and PVC creation events within sensitive namespaces. Use Kubernetes audit logs to identify unusual export operations or PVC modifications by service accounts. Network-based detection is limited since the attack occurs within the cluster; focus on pod-level file access auditing and symlink creation patterns. Consider deploying file integrity monitoring on exporter pods to detect unauthorized file reads.

Why prioritize this

This vulnerability merits prompt attention despite requiring authentication. The CVSS score of 7.7 (HIGH) reflects the combination of network accessibility, low complexity, and confidentiality impact. Organizations using KubeVirt in multi-tenant environments or handling sensitive data should prioritize patching. The lack of KEV designation suggests active exploitation may be limited, but the ease of exploitation post-compromise warrants prioritization before attackers gain broader awareness.

Risk score, explained

The CVSS 3.1 score of 7.7 (HIGH) is derived from: (1) Network vector—the vulnerability is reachable over the network via Kubernetes API; (2) Low complexity—no unusual conditions or privilege escalation required beyond namespace access; (3) Low privilege requirement—namespace-level permissions suffice; (4) No user interaction; (5) Changed scope—the compromise can affect confidentiality of data across the cluster scope; and (6) High confidentiality impact—arbitrary file read capability. The score appropriately reflects a meaningful but not critical risk, consistent with the authentication requirement.

Frequently asked questions