CVE 8.7 HIGH

Long-poll NDJSON body splitting causes unbounded memory allocation in Phoenix_CVE-2026-32689

8.7 / 10
HIGH
CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:N/VI:N/VA:H/SC:N/SI:N/SA:N

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 Analysis

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

Basic Information

ID CVE-2026-32689
Source EEF
Published May 5, 2026 at 15:17
Modified May 5, 2026 at 15:41

Affected Product

Vendor phoenixframework
Product phoenix
Version 1.7.0
Affected Versions phoenixframework phoenix 1.7.0
phoenixframework phoenix 1.8.0
phoenixframework phoenix 2674c6ea30634667f9b09966b90269393b445953

CWE Classification

AI Assessment

AI Score 8.7 / 10
AI Severity High
Vendor Phoenix Framework
Product Phoenix
Version 1.7.0-1.7.21, 1.8.0-1.8.5

References

💭 Join the Security Discussion

🔒 Your email address will not be published. Required fields are marked *

⚠️ Please be respectful and constructive in your comments. Security discussions should remain professional.