CVE-2026-23943: CWE-409 Improper Handling of Highly Compressed Data (Data Amplification) in Erlang OTP
CVE-2026-23943 is a medium severity vulnerability in Erlang OTP's SSH transport layer involving improper handling of highly compressed data, also known as a compression bomb. The vulnerability allows an unauthenticated attacker to cause a denial of service via memory exhaustion by sending specially crafted compressed SSH packets that decompress to a much larger size. Two compression algorithms are affected: zlib (activates immediately after key exchange) and zlib@openssh. com (activates post-authentication). This issue affects OTP versions from 17. 0 up to 28. 4. 1 and related SSH versions. No patch information is provided in the available data. The vulnerability can cause out-of-memory kills in memory-constrained environments due to the high decompression amplification ratio.
AI Analysis
Technical Summary
This vulnerability (CVE-2026-23943) in Erlang OTP's ssh_transport modules arises from improper handling of highly compressed data, enabling a denial of service via resource depletion. The SSH transport layer advertises legacy zlib compression by default and decompresses attacker-controlled payloads without size limits pre-authentication, allowing unauthenticated memory exhaustion attacks. The affected compression algorithms are zlib (immediate activation after key exchange) and zlib@openssh.com (post-authentication). Each SSH packet can decompress approximately 255 MB from 256 KB of wire data, resulting in a 1029:1 amplification ratio. Multiple packets can rapidly exhaust available memory, causing out-of-memory kills especially in constrained environments. The vulnerability affects OTP versions from 17.0 through 28.4.1 and corresponding SSH versions from 3.0.1 through 5.5.1 and related subversions. The affected code is located in lib/ssh/src/ssh_transport.erl, specifically in ssh_transport:decompress/2 and ssh_transport:handle_packet_part/4.
Potential Impact
An attacker can cause a denial of service condition by sending specially crafted compressed SSH packets that decompress to a large size, exhausting system memory and potentially causing the SSH service or host to crash. The attack can be performed unauthenticated due to the zlib compression activating immediately after key exchange. This can disrupt availability of systems running affected Erlang OTP versions, particularly in memory-constrained environments.
Mitigation Recommendations
Patch status is not yet confirmed — check the vendor advisory for current remediation guidance. In the absence of an official fix, consider disabling legacy zlib compression in the SSH transport layer if configurable, or applying resource limits to SSH processes to mitigate memory exhaustion. Monitor vendor channels for updates and apply patches promptly once available.
CVE-2026-23943: CWE-409 Improper Handling of Highly Compressed Data (Data Amplification) in Erlang OTP
Description
CVE-2026-23943 is a medium severity vulnerability in Erlang OTP's SSH transport layer involving improper handling of highly compressed data, also known as a compression bomb. The vulnerability allows an unauthenticated attacker to cause a denial of service via memory exhaustion by sending specially crafted compressed SSH packets that decompress to a much larger size. Two compression algorithms are affected: zlib (activates immediately after key exchange) and zlib@openssh. com (activates post-authentication). This issue affects OTP versions from 17. 0 up to 28. 4. 1 and related SSH versions. No patch information is provided in the available data. The vulnerability can cause out-of-memory kills in memory-constrained environments due to the high decompression amplification ratio.
AI-Powered Analysis
Machine-generated threat intelligence
Technical Analysis
This vulnerability (CVE-2026-23943) in Erlang OTP's ssh_transport modules arises from improper handling of highly compressed data, enabling a denial of service via resource depletion. The SSH transport layer advertises legacy zlib compression by default and decompresses attacker-controlled payloads without size limits pre-authentication, allowing unauthenticated memory exhaustion attacks. The affected compression algorithms are zlib (immediate activation after key exchange) and zlib@openssh.com (post-authentication). Each SSH packet can decompress approximately 255 MB from 256 KB of wire data, resulting in a 1029:1 amplification ratio. Multiple packets can rapidly exhaust available memory, causing out-of-memory kills especially in constrained environments. The vulnerability affects OTP versions from 17.0 through 28.4.1 and corresponding SSH versions from 3.0.1 through 5.5.1 and related subversions. The affected code is located in lib/ssh/src/ssh_transport.erl, specifically in ssh_transport:decompress/2 and ssh_transport:handle_packet_part/4.
Potential Impact
An attacker can cause a denial of service condition by sending specially crafted compressed SSH packets that decompress to a large size, exhausting system memory and potentially causing the SSH service or host to crash. The attack can be performed unauthenticated due to the zlib compression activating immediately after key exchange. This can disrupt availability of systems running affected Erlang OTP versions, particularly in memory-constrained environments.
Mitigation Recommendations
Patch status is not yet confirmed — check the vendor advisory for current remediation guidance. In the absence of an official fix, consider disabling legacy zlib compression in the SSH transport layer if configurable, or applying resource limits to SSH processes to mitigate memory exhaustion. Monitor vendor channels for updates and apply patches promptly once available.
Technical Details
- Data Version
- 5.2
- Assigner Short Name
- EEF
- Date Reserved
- 2026-01-19T14:23:14.343Z
- Cvss Version
- 4.0
- State
- PUBLISHED
Threat ID: 69b3d90e2f860ef943bac72f
Added to database: 3/13/2026, 9:29:50 AM
Last enriched: 4/14/2026, 4:04:02 PM
Last updated: 4/27/2026, 5:32:50 PM
Views: 142
Community Reviews
0 reviewsCrowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.
Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.
Actions
Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.
Need more coverage?
Upgrade to Pro Console for AI refresh and higher limits.
For incident response and remediation, OffSeq services can help resolve threats faster.
Latest Threats
Check if your credentials are on the dark web
Instant breach scanning across billions of leaked records. Free tier available.