How severe is GHSA-628h-q48j-jr6q?

No CVSS score has been assigned to GHSA-628h-q48j-jr6q yet. Review the advisory details and affected package list to assess your exposure.

Which packages are affected by GHSA-628h-q48j-jr6q?

GHSA-628h-q48j-jr6q affects the following packages: phoenix (Hex), phoenix (Hex). Ecosystems affected: Hex.

How do I fix GHSA-628h-q48j-jr6q?

Update phoenix to 1.7.22 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-628h-q48j-jr6q is resolved across your whole dependency graph.

How do I detect GHSA-628h-q48j-jr6q in my Hex dependencies?

Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for phoenix. O3's reachability analysis confirms whether the vulnerable code path is actually invoked in your application, so you act on real exposure instead of every transitive match.

How do I mitigate GHSA-628h-q48j-jr6q if there is no patch (or I can't update yet)?

If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.

How does O3 Security protect against GHSA-628h-q48j-jr6q?

O3 pinpoints whether GHSA-628h-q48j-jr6q is reachable in your code and exactly where to fix it, then blocks exploitation in production at runtime until the patched version is deployed.

Is GHSA-628h-q48j-jr6q actively exploited in the wild?

No public exploit code has been indexed for GHSA-628h-q48j-jr6q yet. This does not mean the vulnerability cannot be exploited — absence of public exploits does not imply safety. Apply the recommended fix and use O3 Security to monitor your exposure.

What type of vulnerability is GHSA-628h-q48j-jr6q?

GHSA-628h-q48j-jr6q is classified as CWE-770 (CWE-770). This weakness type describe the underlying flaw category, which helps determine the potential impact and the right class of mitigation.

When was GHSA-628h-q48j-jr6q published, and has it been updated?

GHSA-628h-q48j-jr6q was published on May 8, 2026 and was last updated on May 8, 2026. Advisory data evolves as severity scores, affected ranges, and exploit intelligence are revised — always check the latest version of the advisory before acting.

💧 Hex

GHSA-628h-q48j-jr6q

Fix: phoenixframework/phoenix@1a67c61

GHSA-628h-q48j-jr6q is a CWE-770 vulnerability in phoenix. O3 Security confirms whether GHSA-628h-q48j-jr6q is actually reachable in your code before you act, and blocks exploitation at runtime until you patch.

Phoenix: Long-poll NDJSON body splitting causes large memory allocation

Also known asCVE-2026-32689EEF-CVE-2026-32689

Published

May 8, 2026

Updated

May 8, 2026

Affected

2 pkgs

Patched

2 / 2

Exploits

None indexed

Real-World Exposure

2 pkgs affected

💧phoenix💧phoenix

Real-time download stats are indexed for npm and PyPI packages. This vulnerability affects Hex packages — download data is not available via public APIs for these ecosystems.

Description

Summary

An unauthenticated denial-of-service vulnerability in Phoenix's long-poll transport allows a remote client to allocate a large amount of memory with a HTTP request. A handful of concurrent requests can be sufficient to let the node run out of memory.

Details

The unoptimised code path exists on the application/x-ndjson POST handling in the LongPoll transport. The endpoint requires only a session token, which any client can obtain by issuing a GET to the same URL with a matching Origin header, so exploitation is unauthenticated.

Impact

Anyone who runs a LiveView app with a public Longpoll socket or uses a Phoenix.Socket with longpoll option. Longpoll has been enabled for newly generated Phoenix projects since Phoenix 1.7.11.

Affected Packages

2 total 2 fixed

Ecosystem	Package	Vulnerable range	Fix
💧Hex	`phoenix`	≥ 1.7.0&&< 1.7.22	1.7.22
💧Hex	`phoenix`	≥ 1.8.0&&< 1.8.6	1.8.6

Detection & mitigation playbook

Open-source dependency

Detect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for phoenix. O3's reachability analysis confirms whether the vulnerable code path is actually invoked in your application, so you act on real exposure instead of every transitive match.
Fix
Update phoenix to 1.7.22 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-628h-q48j-jr6q is resolved across your whole dependency graph.
Workarounds
If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.
How O3 protects you
O3 pinpoints whether GHSA-628h-q48j-jr6q is reachable in your code and exactly where to fix it, then blocks exploitation in production at runtime until the patched version is deployed.

Tailored to GHSA-628h-q48j-jr6q. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.

Frequently Asked Questions

### Summary An unauthenticated denial-of-service vulnerability in Phoenix's long-poll transport allows a remote client to allocate a large amount of memory with a HTTP request. A handful of concurrent requests can be sufficient to let the node run out of memory. See also https://cna.erlef.org/cves/CVE-2026-32689.html. ### Details The unoptimised code path exists on the `application/x-ndjson` POST handling in the LongPoll transport. The endpoint requires only a session token, which any client can obtain by issuing a GET to the same URL with a matching `Origin` header, so exploitation is una

O3 Security · Impact-Aware SCA

Is GHSA-628h-q48j-jr6q in your dependencies?

O3 detects GHSA-628h-q48j-jr6q across Hex dependencies and uses function-level reachability to confirm whether the vulnerable code path is actually reachable — not just present. No false positives.

Scan my dependencies How O3 SCA works