Vulnerability in Erlang OTP ssh (CVE-2025-48039)
Summary
Vulnerability in Erlang OTP ssh (CVE-2025-48039). Risk of unauthorized operations or information disclosure.
Original description
The description as published by the source.
Summary
Allocation of Resources Without Limits or Throttling vulnerability in Erlang OTP ssh (ssh_sftp modules) allows Excessive Allocation, Resource Leak Exposure. This vulnerability is associated with program files lib/ssh/src/ssh_sftpd.erl.
This issue affects OTP from OTP 17.0 until OTP 28.0.3, OTP 27.3.4.3 and 26.2.5.15 corresponding to ssh from 3.0.1 until 5.3.3, 5.2.11.3 and 5.1.4.12.
Workaround
- Disable sftp
- limiting number of max_sessions allowed for sshd, so exploiting becomes more complicated
Configuration
The SFTP subsystem must be enabled on the SSH server and the SSH port must be reachable by the attacker. SFTP is enabled by default unless explicitly disabled by setting {subsystems, []} in the SSH daemon configuration.
Source: OSV.dev (Open Source Vulnerabilities) NVD GitHub Advisory OSV
Auto-generated summary
Assembled by SecPulse from the source data (CVSS, CWE, affected versions) using templates — no AI involved. Check the original description and references below for exact details.
A vulnerability tracked as CVE-2025-48039 has been found in Erlang OTP ssh.
Risk of unauthorized operations or information disclosure.
What to do: apply the vendor's official patched release.
If unsure, ask your IT team or search "Erlang OTP ssh CVE-2025-48039" on the vendor's site.
CVE-2025-48039 (Erlang OTP ssh) — CWE-400
Plan: 1) Audit SBOM/dependencies, 2) Stage→prod upgrade, 3) Add WAF/proxy monitoring on affected endpoints, 4) Hunt IOCs in logs.
Refs: see the GHSA / vendor advisory / patched release linked on this page.
A vulnerability (CWE-400) exists in Erlang OTP ssh.
Check the vendor advisory for the affected versions of Erlang OTP ssh.
Severity: ?. Risk of unauthorized operations or information disclosure.
Update to the patched release per vendor advisory.
Until the patch is applied: disable the affected feature, apply WAF rules, or restrict access via network ACLs.
Search webserver/proxy logs for unusual request patterns matching this CVE's known IOCs. Audit SBOM/dependencies to find affected services.
Response actions
Concrete steps and command examples for SOC/SRE teams to execute in order
-
1Identify exposure identify
Audit SBOM/dependencies for affected components.資産台帳・SBOM・依存マニフェストで Erlang OTP ssh を使っているサービスとバージョンを洗い出す。
-
2Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。
Fix status by distribution
Fixed packages published by each distribution for this CVE
- Debian DEBIAN-CVE-2025-48039 erlang Fixed in: 1:23.2.6+dfsg-1+deb11u3
- Ubuntu UBUNTU-CVE-2025-48039 erlang Fixed in: 1:16.b.3-dfsg-1ubuntu2.2+esm1
References
- web github.com
- web cna.erlef.org
- web erlang.org
- web github.com
- web github.com
- web github.com
- web osv.dev