CVE-2026-32689: CWE-770 Allocation of Resources Without Limits or Throttling in phoenixframework phoenix
Allocation of Resources Without Limits or Throttling vulnerability in phoenixframework phoenix allows a denial of service via the long-poll transport's NDJSON body handling. In 'Elixir.Phoenix.Transports.LongPoll':publish/4, when a POST request is received with Content-Type: application/x-ndjson, the request body is split on newline characters using String.split/2 with no limit on the number of resulting segments. An attacker can send a body consisting entirely of newline bytes, causing a 1:1 amplification into a list of empty binaries — a 1 MB body produces approximately one million list elements, an 8 MB body approximately 8.4 million. Each element is then walked by Enum.map, materializing another list of the same size. This exhausts BEAM memory and schedulers, crashing the node and terminating all active sessions. A session token required to reach the vulnerable endpoint is freely obtainable by any client via an unauthenticated GET request to the same URL with a matching Origin header, making this attack effectively unauthenticated. This issue affects phoenix: from 1.7.0 before 1.7.22 and 1.8.6.
AI Analysis
Technical Summary
This vulnerability (CVE-2026-32689) in phoenixframework phoenix involves improper handling of NDJSON request bodies in the long-poll transport's publish/4 function. Specifically, when a POST request with Content-Type application/x-ndjson is received, the body is split on newline characters without limiting the number of segments. An attacker can exploit this by sending a body composed entirely of newline bytes, causing a massive amplification in list elements that exhausts BEAM memory and schedulers, leading to a node crash and termination of all active sessions. The required session token can be obtained unauthenticated via a GET request with a matching Origin header, making the attack effectively unauthenticated. Affected versions include phoenix 1.7.0 up to but not including 1.7.22 and 1.8.6.
Potential Impact
Successful exploitation results in denial of service by crashing the phoenix node, terminating all active sessions. The vulnerability allows unauthenticated attackers to exhaust server resources, causing service disruption. There are no indications of code execution or data breach from the provided information.
Mitigation Recommendations
Patch status is not yet confirmed — check the vendor advisory for current remediation guidance. No official fix or temporary workaround is documented in the provided data. Until a patch is available, consider restricting or validating NDJSON payload sizes and monitoring for abnormal request patterns targeting the long-poll transport endpoint.
CVE-2026-32689: CWE-770 Allocation of Resources Without Limits or Throttling in phoenixframework phoenix
Description
Allocation of Resources Without Limits or Throttling vulnerability in phoenixframework phoenix allows a denial of service via the long-poll transport's NDJSON body handling. In 'Elixir.Phoenix.Transports.LongPoll':publish/4, when a POST request is received with Content-Type: application/x-ndjson, the request body is split on newline characters using String.split/2 with no limit on the number of resulting segments. An attacker can send a body consisting entirely of newline bytes, causing a 1:1 amplification into a list of empty binaries — a 1 MB body produces approximately one million list elements, an 8 MB body approximately 8.4 million. Each element is then walked by Enum.map, materializing another list of the same size. This exhausts BEAM memory and schedulers, crashing the node and terminating all active sessions. A session token required to reach the vulnerable endpoint is freely obtainable by any client via an unauthenticated GET request to the same URL with a matching Origin header, making this attack effectively unauthenticated. This issue affects phoenix: from 1.7.0 before 1.7.22 and 1.8.6.
AI-Powered Analysis
Machine-generated threat intelligence
Technical Analysis
This vulnerability (CVE-2026-32689) in phoenixframework phoenix involves improper handling of NDJSON request bodies in the long-poll transport's publish/4 function. Specifically, when a POST request with Content-Type application/x-ndjson is received, the body is split on newline characters without limiting the number of segments. An attacker can exploit this by sending a body composed entirely of newline bytes, causing a massive amplification in list elements that exhausts BEAM memory and schedulers, leading to a node crash and termination of all active sessions. The required session token can be obtained unauthenticated via a GET request with a matching Origin header, making the attack effectively unauthenticated. Affected versions include phoenix 1.7.0 up to but not including 1.7.22 and 1.8.6.
Potential Impact
Successful exploitation results in denial of service by crashing the phoenix node, terminating all active sessions. The vulnerability allows unauthenticated attackers to exhaust server resources, causing service disruption. There are no indications of code execution or data breach from the provided information.
Mitigation Recommendations
Patch status is not yet confirmed — check the vendor advisory for current remediation guidance. No official fix or temporary workaround is documented in the provided data. Until a patch is available, consider restricting or validating NDJSON payload sizes and monitoring for abnormal request patterns targeting the long-poll transport endpoint.
Technical Details
- Data Version
- 5.2
- Assigner Short Name
- EEF
- Date Reserved
- 2026-03-13T09:12:14.475Z
- Cvss Version
- 4.0
- State
- PUBLISHED
- Remediation Level
- null
Threat ID: 69fa191dcbff5d86100ff6c1
Added to database: 5/5/2026, 4:21:49 PM
Last enriched: 5/5/2026, 4:37:08 PM
Last updated: 5/6/2026, 3:29:15 AM
Views: 5
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.