CVE-2026-57966: Path Traversal in spice-vdagent File Transfers

Technical summary

CVE-2026-57966 is a CWE-22 path traversal vulnerability in spice-vdagent's file transfer handling. The vulnerability stems from insufficient input sanitization on filenames received from a SPICE host during file operations. An attacker positioned as or controlling the SPICE host can craft filenames containing directory traversal sequences (e.g., '../') to write files outside intended directories. The write operation executes with the privilege level of the spice-vdagent process—typically that of the logged-in user—meaning sensitive application or system files could be overwritten or created. The attack surface is local to the guest environment; remote exploitation is not possible without prior compromise of the SPICE infrastructure.

Business impact

In virtualized or cloud environments leveraging SPICE for guest management, this vulnerability creates a post-compromise escalation path. If a SPICE host is breached or if an insider has malicious intent toward guest systems, attackers gain the ability to plant malware, modify configuration files, inject code into startup sequences, or disable security tools—all running as a regular user without requiring additional privilege escalation. For organizations running untrusted or semi-trusted SPICE hosts, the risk is elevated. For environments with strict host integrity controls, impact is substantially reduced.

Affected systems

Red Hat Enterprise Linux systems using spice-vdagent are affected across multiple versions. The spice-vdagent package itself is the direct vector. Any guest operating system running a vulnerable version of spice-vdagent on a SPICE-capable hypervisor (QEMU/KVM with SPICE protocol) is in scope. Windows and Linux guests are both potentially affected if running the vulnerable agent. Verify the exact affected versions against Red Hat security advisories and the upstream SPICE project.

Exploitability

This vulnerability requires an attacker to already control or compromise the SPICE host—a privileged position in a virtualization infrastructure. It does not allow unauthenticated remote code execution over the network. Exploitation is straightforward once that precondition is met: craft a file transfer request with a traversal payload in the filename. The CVSS score of 4.4 (MEDIUM) reflects this requirement; the local attack vector and high integrity impact are balanced by the need for high privilege on the host side. No public exploit code or active weaponization is currently tracked.

Remediation

Apply vendor security updates to spice-vdagent as released by Red Hat and the SPICE project. Patches will implement proper filename sanitization, stripping or rejecting directory traversal sequences before file write operations. Verify patch application across all guest systems in your environment. As an interim control, restrict SPICE host access to trusted administrators and monitor file transfer activity in guest logs.

Patch guidance

Consult Red Hat's security advisory for CVE-2026-57966 to identify the patched spice-vdagent version for your Enterprise Linux release. Test patches in a non-production environment first. Patch deployment should prioritize systems in high-trust environments or those hosting sensitive workloads. Coordinate patching with your virtualization team to ensure guest consistency and to validate that file transfer functionality is not disrupted post-patch. Consider using configuration management tools to standardize versions across your fleet.

Detection guidance

Monitor spice-vdagent process activity and file write operations for suspicious patterns: files being written to system directories, unexpected modifications to sensitive paths, or filenames containing '../' or absolute paths in file transfer logs. Hypervisor-level logging (QEMU/KVM event logs) may record unusual file transfer requests. Check guest system file integrity monitoring tools for unexpected changes in critical system directories. Correlate spice-vdagent process creation and file operations with user and host activity to identify potential compromise.

Why prioritize this

While the CVSS score is MEDIUM (4.4), prioritization should reflect your virtualization trust model. Organizations with strict SPICE host access controls can defer patching to normal maintenance windows. Those running SPICE in less-controlled environments—for example, development teams with broad host access, or multi-tenant scenarios—should prioritize higher. The vulnerability poses real risk only if the attacker is already positioned at the host, making it a secondary or tertiary stage in an attack chain rather than a direct entry point.

Risk score, explained

The CVSS 3.1 score of 4.4 reflects: (AV:L) local attack vector—the attacker must be on or control the SPICE host; (AC:L) low attack complexity—once positioned, exploitation is trivial; (PR:H) high privilege requirement—the attacker must be a privileged SPICE host component or process; (UI:N) no user interaction—the guest user need not take action; (S:U) no scope change—impact is limited to the guest system; (C:N) no confidentiality impact; (I:H) high integrity impact—arbitrary file write; (A:N) no availability impact. The MEDIUM rating appropriately weights the serious integrity risk against the high barrier to initial access.

Frequently asked questions