Skip to content
Patch Next
Sign inAdd to your agent

← Actionable
Unrated

FTP command injection via CRLF in control channel arguments

GHSA-8mhj-xm4h-m5m6

What to do

Vendor fix available. Upgrade each affected package to the fixed version on its release line (suppaftp 10.0.2), redeploy, then verify what is actually installed.

This page has no inventory attached, so it cannot say whether you are affected. A vendor fix is not proof that your deployment is fixed.

Add to your agent

Affected packages

  • crates.io suppaftp

    Affected
    >= 0.0.0-0, < 10.0.2
    Fixed in
    10.0.2

Sources

Severity and exploitation
Exploitation
No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.
CVSS
not scored
EPSS
No dated EPSS signal available.
Source description

As published by the source; long descriptions are shortened.

Affected versions of `suppaftp` wrote command arguments (user name, password, paths, `SITE` arguments and custom commands) to the FTP control channel without validation. An argument containing a carriage return (`\r`) or a line feed (`\n`) terminated the intended command line and let a second, attacker-chosen command be sent to the server within the same authenticated session. An application that passes untrusted input as credentials, paths or command strings to methods such as `login`, `cwd`, `mkdir`, `rmdir`, `rm`, `rename`, `retr`, `put_file`, `site` or `custom_command` can therefore be made to execute arbitrary FTP commands with the application's privileges, for example deleting files or redirecting a data connection with an injected `PORT`. All three clients are affected: sync, tokio and smol, with or without TLS. The flaw was corrected in version 10.0.2 (commit 194bdd1): every command line is…

Dates and revisions
Published by the source
Last modified by the source
Source last checked
  1. Revision 1 · created ·

    Published from osv record RUSTSEC-2026-0271

Agent brief

Preview the exact text before you copy it. Commands are read-only suggestions; review them before running anything.

# Patch Next advisory brief: GHSA-8mhj-xm4h-m5m6

Advisory: FTP command injection via CRLF in control channel arguments
IDs: GHSA-8mhj-xm4h-m5m6
Record: https://patchnext.com/advisories/rustsec-2026-0271 (revision 1, source checked 23 Oct 2026, 22:04 UTC)
Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected.
Severity: Unrated
Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV.
Vendor response: Vendor fix available; fixed versions by package: suppaftp 10.0.2. A vendor fix does not mean a deployment is fixed.

## Affected components
- crates.io suppaftp: affected >= 0.0.0-0, < 10.0.2; fixed in 10.0.2

## Suggested inspection (read-only)
- crates.io suppaftp: check the installed version with your package manager.

## Supported action
Upgrade each affected component to a fixed version on its release line. For a transitive dependency, upgrade the parent package or add an override or constraint, then regenerate the lockfile. Redeploy every environment that ran an affected version.

## Required regression checks
- Run the test suite and a production build.
- Exercise the features that depend on suppaftp.
- Repeat the inspection and confirm that only fixed versions remain installed.

## Rollback considerations
- Keep the previous lockfile and deployment artifact. Rolling back reinstates the vulnerable version, so apply any documented mitigation while you fix forward.

## Unresolved questions
- Which deployments run an affected version?
- Exploitation status can change. Check again before lowering the priority.
- Mark the work resolved only after the fixed version is verified in production.

## Sources
- Verified: https://osv.dev/vulnerability/RUSTSEC-2026-0271 (OSV record RUSTSEC-2026-0271 lists affected ranges: crates.io suppaftp >=0.0.0-0 <10.0.2 (fixed))

Commands are suggestions: review each one before running it.

Loading voting…