CVE-2025-48040: Malicious Key Exchange Messages may Lead to Excessive Resource Consumption
Uncontrolled Resource Consumption vulnerability in Erlang OTP ssh (ssh_sftp modules) allows Excessive Allocation, Flooding. 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.
Security readout for executives and security teams
Plain-English summary
CVE-2025-48040 is a denial-of-service risk in Erlang/OTP's SSH SFTP code. A remote, unauthenticated attacker could send malicious SSH key exchange messages that cause excessive resource use, potentially reducing service availability. The available sources do not show data theft or code execution impact.
Executive priority
Treat as a near-term availability fix for exposed Erlang/OTP SSH/SFTP services. It is not evidenced as exploited or data-compromising, but unauthenticated network reachability makes outage risk credible.
Technical view
The issue is uncontrolled resource consumption in Erlang OTP ssh_sftp modules, associated with lib/ssh/src/ssh_sftpd.erl. It is mapped to CWE-400 and CWE-770, with CVSS 4.0 score 6.9. Affected ranges span OTP 17.0 through specified 26, 27, and 28 branch levels, corresponding to ssh 3.0.1 through listed branch versions.
Likely exposure
Exposure is most likely where Erlang/OTP applications run the OTP SSH/SFTP server component on a network-reachable interface. Systems using affected OTP versions but not enabling ssh_sftp are less likely to be exposed. Internet-facing SSH/SFTP services should be prioritized.
Exploitation context
The bundle marks KEV as false, and no cited source states active exploitation. The vulnerability is remotely reachable, low complexity, unauthenticated, and availability-focused. Evidence provided does not support claims of code execution, privilege escalation, or confidentiality impact.
Researcher notes
The source bundle indicates affected OTP versions from 17.0 through branch-specific upper bounds and references upstream patches. Exact fixed-release interpretation should be confirmed against Erlang advisory wording before enforcement. Focus validation on ssh_sftpd usage, not merely OTP presence.
Mitigation direction
Apply Erlang/OTP vendor updates or patches from the advisory and linked commits.
Prioritize internet-facing OTP SSH/SFTP services before internal-only deployments.
Restrict network access to OTP SSH/SFTP services where business requirements allow.
Monitor vendor guidance for exact fixed branch versions and backports.
Use operational rate limiting or connection controls where available.
Validation and detection
Inventory Erlang/OTP versions and included ssh application versions.
Confirm whether the OTP ssh_sftp server module is enabled or reachable.
Compare deployed versions against the vendor advisory affected ranges.
Review external exposure for OTP-based SSH/SFTP endpoints.
Verify patched builds include the referenced upstream fixes.
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Potential ATT&CK relevance
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
cwe · low confidence lookup
CWE-400: Exact CWE lookup
Use the exact CWE identifier as the starting point before reviewing related ATT&CK behavior. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
Use the exact CWE identifier as the starting point before reviewing related ATT&CK behavior. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.
We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.