Erlang · Erlang/OTP · published 2026-06-10
CVE-2026-48858ftp client PASV response IP not validated against control peer, enabling SSRF and FTP bounce attacks
Routine No exploitation evidence; EPSS 0.2%.
CVE-2026-48858 is not known to be exploited in the wild. EPSS estimates a 0.2% chance of exploitation in the next 30 days, higher than 14% of all CVEs. This Erlang/OTP vulnerability: CVSS 6.3 (v4.0), attacks can be automated. Fixed upstream in Erlang/OTP 29.1.2, 29.0.2, 28.5.0.8, 28.5.0.2 (+2 more). Routine: patch when convenient.
Jump to: Remediation Exploit intelAffected versionsDescription
Remediation#
Fixed upstream in Erlang/OTP 29.1.2, 29.0.2, 28.5.0.8, 28.5.0.2, 27.3.4.19, 27.3.4.13.
Patch events
Language runtimeErlang/OTP
Erlang/OTP security fixes: 7 CVEs
Upgrade to
29.1.229.0.228.5.0.828.5.0.227.3.4.1927.3.4.13Why: Vendor security release for server software (most severe: CVE-2026-49759).
Exploit intelligence#
| Signal | Value | Source |
|---|---|---|
| Known exploited | No | CISA KEV |
| Ransomware use | — | CISA KEV |
| EPSS (30-day exploitation probability) | 0.2% (15th pct) | FIRST EPSS v2026.06.15 |
| CVSS base score | 6.3 (v4.0)CVSS:4.0/AV:N/AC:L/AT:P/PR:N/UI:N/VC:L/VI:L/VA:N/SC:L/SI:L/SA:N | CNA / CISA ADP |
| SSVC exploitation | none | CISA Vulnrichment |
| SSVC automatable | Yes | CISA Vulnrichment |
| SSVC technical impact | partial | CISA Vulnrichment |
Affected versions (from the CVE record)#
- Erlang OTP
17.4to before*(affected)
- Erlang OTP
5.10.4to before7.0(affected)
- Erlang OTP
1.0to before*(affected)
- Erlang OTP
be95772ee1fcfe71045ef070130bea7a910b81e3to before*(affected)
Description (from the CVE record)#
Server-Side Request Forgery (SSRF) vulnerability in Erlang/OTP ftp (ftp_internal module) allows FTP bounce attacks and SSRF via an unvalidated PASV response IP address. The ftp_internal:handle_ctrl_result/2 PASV handler (mode=passive, ipfamily=inet, ftp_extension=false) extracts the IP address from the server's 227 response and passes it directly to gen_tcp:connect/4 without validating it against the control connection peer address. The adjacent EPSV handlers correctly call peername(CSock) to derive the IP from the control connection, but the PASV handler does not. A malicious or compromised FTP server can redirect the client's data connection to an arbitrary internal host and port. On read operations (ftp:ls/1,2, ftp:nlist/1,2, ftp:recv/2,3), data from the redirected target is returned to the caller. On write operations (ftp:send/2,3, ftp:append/2,3), file content is sent to the redirected target. This enables SSRF against internal hosts, cloud metadata endpoints, and FTP bounce attacks against third-party hosts. The vulnerable path is the default configuration (mode=passive, ipfamily=inet, ftp_extension=false). RFC 2577 section 3 explicitly recommends validating the PASV response IP against the control connection peer. The ftp application is deprecated and scheduled for removal in OTP-30. This vulnerability is associated with program files lib/inets/src/ftp/ftp_internal.erl (inets 5.10.4 through 6.5, OTP 17.4 through 20.3) and lib/ftp/src/ftp_internal.erl (ftp 1.0 and later, OTP 21.0 and later). This issue affects OTP from OTP 17.4 before OTP 27.3.4.13, OTP 28.5.0.2, and OTP 29.0.2, corresponding to inets from 5.10.4 before 7.0, and ftp from 1.0 before 1.2.3.1, 1.2.4.1, and 1.2.6.
Quoted from the CVE Program record.