# CVE-2026-28296: Gvfs: ftp gvfs backend: arbitrary ftp command injection via crlf sequences in file paths

> Remote attackers can inject arbitrary FTP commands via CRLF sequences in file paths, potentially leading to arbitrary code execution.

- **Severity:** Medium 4.3 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:L/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** A user has to click or open something
- **Fix available:** Yes
- **Published:** 26 Feb 2026
- **Updated:** 26 Feb 2026
- **Also known as:** DEBIAN-CVE-2026-28296, GHSA-r8j5-pj3m-qhpv, OESA-2026-2570, OESA-2026-2571, OESA-2026-2670, UBUNTU-CVE-2026-28296

## What is CVE-2026-28296?

CVE-2026-28296 is a medium-severity command injection vulnerability in Red Hat Enterprise Linux 10, published on 26 Feb 2026. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.

### Official description

A flaw was found in the FTP GVfs backend. A remote attacker could exploit this input validation vulnerability by supplying specially crafted file paths containing carriage return and line feed (CRLF) sequences. These unsanitized sequences allow the attacker to terminate intended FTP commands and inject arbitrary FTP commands, potentially leading to arbitrary code execution or other severe impacts.

Weakness: CWE-93 (Improper Neutralization of CRLF Sequences)

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


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

Apply the vendor's patch.

## Is CVE-2026-28296 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-28296 is a medium-severity command injection vulnerability in Red Hat Enterprise Linux 10, published on 26 Feb 2026. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2026-28296 in the wild and no public exploit code.

Affected product: Red Hat Enterprise Linux 10. 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-28296/ (Markdown: https://insights.sbomify.com/CVE-2026-28296/index.md)
```

## Sources

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

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