CVE REMEDIATION GUIDE
Review reviewHighFixed-version data available

CVE-2026-39983 remediation guide

patrickjuchli basic-ftp, Red Hat Developer Hub 1.8, Red Hat Developer Hub 1.9

basic-ftp is an FTP client for Node.js. Prior to 5.2.1, basic-ftp allows FTP command injection via CRLF sequences (\r\n) in file path parameters passed to high-level path APIs such as cd(), remove(), rename(), uploadFrom(), downloadTo(), list(), and removeDir(). The library's protectWhitespace() helper only handles leading spaces and returns other paths unchanged, while FtpContext.send() writes the resulting command string directly to the control socket with \r\n appended. This lets attacker-controlled path strings split one intended FTP command into multiple commands. This vulnerability is...

Open CVE record
Productpatrickjuchli basic-ftp, Red Hat Developer Hub 1.8, Red Hat Developer Hub 1.9
Affected versions>= < 5.2.1, < 5.2.1
Fixed versions5.2.1
Priority basisReview · CVSS 8.6 · EPSS 2.19%
01

Identify the affected asset

Confirm whether patrickjuchli basic-ftp, Red Hat Developer Hub 1.8, Red Hat Developer Hub 1.9 is installed, record the deployed version and installation path, and identify exposed interfaces.

  • Record the product name, package or appliance identifier, and installed version.
  • Identify internet-facing, administrative, API, and internal access paths.
  • Preserve the pre-change configuration and relevant service logs.
02

Validate the affected-version match

Compare the deployed version with the affected range: >= < 5.2.1, < 5.2.1. Treat incomplete inventory results as unresolved.

03

Prioritize with independent signals

The CVSS severity warrants an early asset and exposure review. Combine this signal with asset criticality, exposure, compensating controls, and business impact.

04

Apply supported remediation

Follow the vendor advisory or supported update path. Current fixed-version status: 5.2.1. Preserve configuration and rollback material before change.

05

Verify the result

Confirm the resulting version, service health, authentication and access paths, monitoring coverage, and relevant security logs.

  • Confirm the expected version and package state.
  • Run a functional health check for critical service paths.
  • Review authentication, error, application, and security monitoring logs.
  • Reassess exposure if the supported fix cannot be applied.

Operational boundary

This page does not replace the vendor advisory, support contract, change-management process, or recovery plan. Do not infer that an asset is unaffected from an incomplete inventory query or a missing fixed-version field.