Allocation of Resources Without Limits or Throttling Affecting phoenix package, versions >=1.7.0 <1.7.22>=1.8.0 <1.8.6
Threat Intelligence
The probability is the direct output of the EPSS model, and conveys an overall sense of the threat of exploitation in the wild. The percentile measures the EPSS probability relative to all known EPSS scores. Note: This data is updated daily, relying on the latest available EPSS model version. Check out the EPSS documentation for more details.
Do your applications use this vulnerable package?
In a few clicks we can analyze your entire application and see what components are vulnerable in your application, and suggest you quick fixes.
Test your applicationsSnyk Learn
Learn about Allocation of Resources Without Limits or Throttling vulnerabilities in an interactive lesson.
Start learning- Snyk IDSNYK-HEX-PHOENIX-16425772
- published6 May 2026
- disclosed5 May 2026
- creditPeter Ullrich
Introduced: 5 May 2026
NewCVE-2026-32689 (opens in a new tab)How to fix?
Upgrade phoenix to version 1.7.22, 1.8.6 or higher.
Overview
phoenix is a Phoenix is a web development framework written in Elixir which implements the server-side Model View Controller (MVC) pattern. Many of its components and concepts will seem familiar to those of us with experience in other web frameworks like Ruby on Rails or Python's Django.
Phoenix provides the best of both worlds - high developer productivity and high application performance. It also has some interesting new twists like channels for implementing realtime features and pre-compiled templates for blazing speed.
Affected versions of this package are vulnerable to Allocation of Resources Without Limits or Throttling via the Elixir.Phoenix.Transports.LongPoll POST requests handling with Content-Type: application/x-ndjson. An attacker can exhaust system memory and schedulers, leading to a crash and termination of all active sessions by sending a large request body consisting entirely of newline bytes, which is split into a massive list of empty binaries and further processed without limits.
Note:
This is only exploitable if the longpoll transport is enabled on any
Phoenix.Socketdeclaration, including the LiveView/livesocket.Longpoll is enabled for newly generated Phoenix projects since Phoenix 1.7.11.
Workaround
This vulnerability can be mitigated by disabling the longpoll transport on all Phoenix.Socket declarations, including the LiveView /live socket, by removing or setting longpoll: false. Note that this prevents clients that cannot use WebSockets from connecting.