CVE-2026-68956: CWE-770 Allocation of Resources Without Limits or Throttling in Erlang OTP
Allocation of Resources Without Limits or Throttling vulnerability in Erlang/OTP ssh allows an authenticated remote attacker to exhaust node memory by repeatedly opening session channels that are never assigned a handler. The "session" clause of ssh_connection:handle_msg/4 checks only minimal_remote_max_packet_size before calling setup_session/5, which unconditionally builds a #channel{} record and stores it in the ETS channel cache. The max_channels daemon option is consulted only by ssh_channel_sup:max_num_channels_not_exceeded/2, which counts supervisor children, so a channel that never gets a shell, exec, or subsystem handler is invisible to the limit and setting the option to a finite value does not mitigate the attack. RFC 4254 section 5.1 permits many session channels per connection, and each record costs only a few hundred bytes, so a single authenticated connection can accumulate channels until the node runs out of memory and the emulator terminates, affecting every application on it. No file contents, credentials, or write access are obtainable. This issue affects OTP from OTP 18.1.2 before OTP 27.3.4.18, OTP 28.5.0.7, and OTP 29.1.1, corresponding to ssh from 4.1.1 before 5.2.11.13, 5.5.2.6, and 6.0.6. Whether OTP before OTP 18.1.2, corresponding to ssh before 4.1.1, is affected is unknown.
AI Analysis
Technical Summary
This vulnerability (CWE-770) in Erlang/OTP ssh occurs because the 'session' clause of ssh_connection:handle_msg/4 only checks minimal_remote_max_packet_size before creating a channel record and storing it in the ETS channel cache. The max_channels daemon option limits only channels with assigned handlers by counting supervisor children, so channels without shell, exec, or subsystem handlers bypass this limit. As RFC 4254 section 5.1 permits many session channels per connection, an attacker with authentication can open many such channels, each consuming memory, eventually exhausting node memory and causing the emulator to terminate. Affected OTP versions are from 17.0 up to but excluding 27.3.4.18, 28.5.0.7, and 29.1.1, corresponding to ssh versions from 3.0.1 up to but excluding 5.2.11.13, 5.5.2.6, and 6.0.6. It is unknown if versions before OTP 17.0 are affected.
Potential Impact
An authenticated remote attacker can cause a denial of service by exhausting the node's memory through repeated opening of session channels without handlers. This leads to termination of the Erlang emulator, affecting all applications running on the node. No unauthorized data access or modification is possible through this vulnerability.
Mitigation Recommendations
Patch status is not yet confirmed — check the vendor advisory for current remediation guidance. Setting the max_channels option to a finite value does not mitigate this attack because channels without handlers are not counted. Until an official fix is available, restrict authenticated access to trusted users only and monitor for unusual ssh session channel activity.
CVE-2026-68956: CWE-770 Allocation of Resources Without Limits or Throttling in Erlang OTP
Description
Allocation of Resources Without Limits or Throttling vulnerability in Erlang/OTP ssh allows an authenticated remote attacker to exhaust node memory by repeatedly opening session channels that are never assigned a handler. The "session" clause of ssh_connection:handle_msg/4 checks only minimal_remote_max_packet_size before calling setup_session/5, which unconditionally builds a #channel{} record and stores it in the ETS channel cache. The max_channels daemon option is consulted only by ssh_channel_sup:max_num_channels_not_exceeded/2, which counts supervisor children, so a channel that never gets a shell, exec, or subsystem handler is invisible to the limit and setting the option to a finite value does not mitigate the attack. RFC 4254 section 5.1 permits many session channels per connection, and each record costs only a few hundred bytes, so a single authenticated connection can accumulate channels until the node runs out of memory and the emulator terminates, affecting every application on it. No file contents, credentials, or write access are obtainable. This issue affects OTP from OTP 18.1.2 before OTP 27.3.4.18, OTP 28.5.0.7, and OTP 29.1.1, corresponding to ssh from 4.1.1 before 5.2.11.13, 5.5.2.6, and 6.0.6. Whether OTP before OTP 18.1.2, corresponding to ssh before 4.1.1, is affected is unknown.
CVSS v4.0
Score 7.1high
Affected software
Erlang
OTP
Erlang
OTP
Erlang
OTP
cpe:2.3:a:erlang:erlang\/otp:*:*:*:*:*:*:*:*Run on your own infrastructure? Check whether these packages are installed with threat-finder — our free open-source scanner.
Weaknesses
AI-Powered Analysis
Machine-generated threat intelligence
Technical Analysis
This vulnerability (CWE-770) in Erlang/OTP ssh occurs because the 'session' clause of ssh_connection:handle_msg/4 only checks minimal_remote_max_packet_size before creating a channel record and storing it in the ETS channel cache. The max_channels daemon option limits only channels with assigned handlers by counting supervisor children, so channels without shell, exec, or subsystem handlers bypass this limit. As RFC 4254 section 5.1 permits many session channels per connection, an attacker with authentication can open many such channels, each consuming memory, eventually exhausting node memory and causing the emulator to terminate. Affected OTP versions are from 17.0 up to but excluding 27.3.4.18, 28.5.0.7, and 29.1.1, corresponding to ssh versions from 3.0.1 up to but excluding 5.2.11.13, 5.5.2.6, and 6.0.6. It is unknown if versions before OTP 17.0 are affected.
Potential Impact
An authenticated remote attacker can cause a denial of service by exhausting the node's memory through repeated opening of session channels without handlers. This leads to termination of the Erlang emulator, affecting all applications running on the node. No unauthorized data access or modification is possible through this vulnerability.
Mitigation Recommendations
Patch status is not yet confirmed — check the vendor advisory for current remediation guidance. Setting the max_channels option to a finite value does not mitigate this attack because channels without handlers are not counted. Until an official fix is available, restrict authenticated access to trusted users only and monitor for unusual ssh session channel activity.
Technical Details
- Data Version
- 5.2
- Assigner Short Name
- EEF
- Date Reserved
- 2026-08-17T13:30:02.155Z
- Cvss Version
- 4.0
- State
- PUBLISHED
Threat ID: 6ab24461f7a7c54106f3e60c
Added to database: 09/22/2026, 09:03:29 UTC
Last enriched: 09/22/2026, 09:17:45 UTC
Last updated: 09/23/2026, 01:58:07 UTC
Views: 46
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.