# CVE-2026-57966: Spice-vdagent: path traversal in file transfer via unsanitized filename

> A malicious SPICE host can write arbitrary files to the guest OS due to unsanitized filenames in spice-vdagent, requiring a compromised host.

- **Severity:** Medium 4.4 (`CVSS:3.1/AV:L/AC:L/PR:H/UI:N/S:U/C:N/I:H/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** An administrator
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 29 Jun 2026
- **Updated:** 29 Jun 2026
- **Also known as:** CLSA-2026-1786552586, DEBIAN-CVE-2026-57966, GHSA-gg66-359m-pmcc, UBUNTU-CVE-2026-57966

## What is CVE-2026-57966?

CVE-2026-57966 is a medium-severity path traversal vulnerability in Redhat Enterprise Linux, published on 29 Jun 2026. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

A path traversal vulnerability was found in spice-vdagent. This flaw allows a malicious or compromised SPICE host to write arbitrary files to any location on the guest operating system. This occurs because the filename provided by the SPICE host during file transfers is not properly sanitized before being used. An attacker could exploit this to write to sensitive locations with the privileges of the spice-vdagent process, typically the logged-in user. This issue requires the SPICE host to be untrusted or compromised for exploitation.

Weakness: CWE-22 (Improper Limitation of a Pathname to a Restricted Directory)

## Which versions are affected by CVE-2026-57966?

It affects 2 products.


Products: Redhat Enterprise Linux, Spice-Space Spice-Vdagent.

## How do I fix CVE-2026-57966?

Apply the vendor's patch.

## Is CVE-2026-57966 being exploited?

There is no known exploitation of CVE-2026-57966 in the wild and no public exploit code.

## Other vulnerabilities in Redhat Enterprise Linux

- [CVE-2018-14667](https://insights.sbomify.com/CVE-2018-14667/): Red Hat JBoss RichFaces Framework Expression Language Injection (critical 9.8, exploited in the wild)
- [CVE-2021-20325](https://insights.sbomify.com/CVE-2021-20325/): Missing fixes for CVE-2021-40438 and CVE-2021-26691 in the versions of httpd, as shipped in Red Hat Enterprise Linux 8.5.0, causes a securit (critical 9.8)
- [CVE-2018-25011](https://insights.sbomify.com/CVE-2018-25011/): Memory corruption in libwebp (critical 9.8)
- [CVE-2018-25014](https://insights.sbomify.com/CVE-2018-25014/): Other in libwebp (critical 9.8)
- [CVE-2014-3585](https://insights.sbomify.com/CVE-2014-3585/): Supply chain in redhat-upgrade-tool (critical 9.8)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-57966 and fix it if it is affected.

What it is: CVE-2026-57966 is a medium-severity path traversal vulnerability in Redhat Enterprise Linux, published on 29 Jun 2026. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-57966 in the wild and no public exploit code.

Affected product: Redhat Enterprise Linux. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-57966/ (Markdown: https://insights.sbomify.com/CVE-2026-57966/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-57966
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-57966
- OSV: https://osv.dev/vulnerability/CVE-2026-57966

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-57966/
Summaries are generated and may contain mistakes; the official description above is the record.