CVE-2025-26618: SSH SFTP packet size not verified properly in Erlang OTP

Published Feb 20, 2025
·
Updated

Erlang is a programming language and runtime system for building massively scalable soft real-time systems with requirements on high availability. OTP is a set of Erlang libraries, which consists of the Erlang runtime system, a number of ready-to-use components mainly written in Erlang. Packet size is not verified properly for SFTP packets. As a result when multiple SSH packets (conforming to max SSH packet size) are received by ssh, they might be combined into an SFTP packet which will exceed the max allowed packet size and potentially cause large amount of memory to be allocated. Note that situation described above can only happen for successfully authenticated users after completing the SSH handshake. This issue has been patched in OTP versions 27.2.4, 26.2.5.9, and 25.3.2.18. There are no known workarounds for this vulnerability.

Other sources

SSH SFTP packet size not verified properly in Erlang OTP

Microsoft

Affected Software

5 affected componentsFixes available
debian/erlang<=1:23.2.6+dfsg-1+deb11u1, <=1:25.2.3+dfsg-1, <=1:25.3.2.12+dfsg-3
1:27.2.4+dfsg-1
Erlang OTP<27.2.4, >=25.3.2<25.3.2.18, >=26.2.5<26.2.5.9
Microsoft azl3 erlang 26.2.5.6-1<26.2.5.9-1
26.2.5.9-1
Microsoft cbl2 erlang 25.2-3<25.2-3
25.2-3
Microsoft azl3 erlang 26.2.5.9-1<26.2.5.9-1
26.2.5.9-1

Remediation

Recommended actions to resolve this vulnerability, in priority order.

  1. Upgrade

    Upgrade debian/erlang to a version that resolves this vulnerability.

    Fixed in 1:27.2.4+dfsg-1
  2. Upgrade

    Upgrade to a fixed release to a version that resolves this vulnerability.

    Fixed in 26.2.5.9-1
  3. Upgrade

    Upgrade to a fixed release to a version that resolves this vulnerability.

    Fixed in 25.2-3
  4. Upgrade

    Upgrade Erlang/OTP to a version that resolves this vulnerability.

    Fixed in 27.2.4
  5. Upgrade

    Upgrade Erlang/OTP to a version that resolves this vulnerability.

    Fixed in 26.2.5.9
  6. Upgrade

    Upgrade Erlang/OTP to a version that resolves this vulnerability.

    Fixed in 25.3.2.18

Event History

Feb 20, 2025
CVE Published
via MITRE·07:04 PM
Data Sourced
via MITRE·07:04 PM
DescriptionWeakness
Data Sourced
via NVD·07:15 PM
DescriptionSeverityWeakness
Mar 3, 2025
Data Sourced
via Ubuntu·06:26 PM
RemedyDescriptionSeverityAffected Software
Mar 4, 2025
Data Sourced
via Microsoft·08:00 AM
DescriptionSeverityWeakness
Data Sourced
via Microsoft·08:00 AM
Affected Software
Updated
via Microsoft·08:00 AM
DescriptionSeverity
Free Weekly Intel

Don't miss critical vulnerabilities

Join thousands of security professionals who receive our weekly digest of trending CVEs, zero-days, and exploited vulnerabilities.

No spam. Unsubscribe anytime.

Frequently Asked Questions

1

What is the severity of CVE-2025-26618?

CVE-2025-26618 is classified as a high severity vulnerability due to potential exploitation risks.

2

How do I fix CVE-2025-26618?

To mitigate CVE-2025-26618, update Erlang OTP to version 27.2.4 or later, or 26.2.5.10 and beyond.

3

What software is affected by CVE-2025-26618?

CVE-2025-26618 affects Erlang OTP versions up to 27.2.4, 26.2.5.9, and 25.3.2.18.

4

What types of systems are impacted by CVE-2025-26618?

CVE-2025-26618 impacts massively scalable soft real-time systems that require high availability.

5

What are the implications of CVE-2025-26618 for developers?

Developers using affected versions of Erlang OTP should prioritize updating to secure their applications against potential exploits.

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co
By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.
© 2026 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203