Server-Side Request Forgery (SSRF) Affecting erlang-sasl package, versions *
Threat Intelligence
The probability is the direct output of the EPSS model, and conveys an overall sense of the threat of exploitation in the wild. The percentile measures the EPSS probability relative to all known EPSS scores. Note: This data is updated daily, relying on the latest available EPSS model version. Check out the EPSS documentation for more details.
Do your applications use this vulnerable package?
In a few clicks we can analyze your entire application and see what components are vulnerable in your application, and suggest you quick fixes.
Test your applicationsSnyk Learn
Learn about Server-Side Request Forgery (SSRF) vulnerabilities in an interactive lesson.
Start learning- Snyk IDSNYK-RHEL8-ERLANGSASL-17362855
- published17 Jun 2026
- disclosed10 Jun 2026
Introduced: 10 Jun 2026
NewCVE-2026-48858 (opens in a new tab)How to fix?
There is no fixed version for RHEL:8 erlang-sasl.
NVD Description
Note: Versions mentioned in the description apply only to the upstream erlang-sasl package and not the erlang-sasl package as distributed by RHEL.
See How to fix? for RHEL:8 relevant fixed versions and status.
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 29.0.2, 28.5.0.2 and 27.3.4.13 corresponding to inets from 5.10.4 before 7.0 and ftp from 1.0 before 1.2.6, 1.2.4.1 and 1.2.3.1.
References
- https://access.redhat.com/security/cve/CVE-2026-48858
- https://cna.erlef.org/cves/CVE-2026-48858.html
- https://github.com/erlang/otp/commit/2691a806231ffd0490a8a9e20500dec0c7e73727
- https://github.com/erlang/otp/commit/521bcfa24407ee8cb5614823cf905c37ea3aa605
- https://github.com/erlang/otp/security/advisories/GHSA-24cv-hwgr-37fq
- https://osv.dev/vulnerability/EEF-CVE-2026-48858
- https://www.erlang.org/doc/system/versions.html#order-of-versions