Vulnerability in phoenix (CVE-2026-56811)
Summary
Vulnerability in phoenix (CVE-2026-56811). Risk of unauthorized operations or information disclosure. Mitigation: upgrade to 1.8.9 or later.
Original description
The description as published by the source.
Summary
Phoenix transports do not limit the number of channels in a given connection, making it easy to spawn hundreds of thousands of processes over a single connection, and, eventually reaching the max processes VM limit. The solution is to limit the number of channels per transport, so an attacker needs to start new HTTP/WebSocket connections, allowing third-party services to apply rate limits and intervene more easily.
Impact
An unauthenticated remote attacker can cause a denial of service against any Phoenix app that exposes LongPoll/WebSocket transports.
Source: NIST National Vulnerability Database NVD GitHub Advisory
Auto-generated summary
Assembled by SecPulse from the source data (CVSS, CWE, affected versions) using templates — no AI involved. Check the original description and references below for exact details.
A vulnerability tracked as CVE-2026-56811 has been found in phoenix.
Risk of unauthorized operations or information disclosure. CVSS score: 7.5/10.
What to do: upgrade phoenix to 1.8.9 or later.
If unsure, ask your IT team or search "phoenix CVE-2026-56811" on the vendor's site.
CVE-2026-56811 (phoenix) — CWE-770 / CVSS v3 7.5
Attack vector: remote (network-reachable) / unauthenticated / no user interaction
Patched: 1.8.9 — apply immediately
Plan: 1) Audit SBOM/dependencies, 2) Stage→prod upgrade, 3) Add WAF/proxy monitoring on affected endpoints, 4) Hunt IOCs in logs.
Refs: see the GHSA / vendor advisory / patched release linked on this page.
A vulnerability (CWE-770) exists in phoenix.
Check the vendor advisory for the affected versions of phoenix.
Severity: High (CVSS 7.5/10). Risk of unauthorized operations or information disclosure.
Update to 1.8.9.
Until the patch is applied: disable the affected feature, apply WAF rules, or restrict access via network ACLs.
Search webserver/proxy logs for unusual request patterns matching this CVE's known IOCs. Run grep -r 'phoenix' . against your dependency files (package-lock.json, requirements.txt, go.sum) to find affected services.
Response actions
Concrete steps and command examples for SOC/SRE teams to execute in order
-
1Identify exposure identify
grep -r 'phoenix' . | grep -v node_modulesリポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で
phoenixを grep し、稼働しているサービス・バージョンを把握する。 -
2Apply patch patch
Upgrade phoenix to 1.8.9ステージング環境で 1.8.9 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスを含めること。
-
3Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。
Affected packages
References
- advisory nvd.nist.gov
- package github.com
- web cna.erlef.org
- web github.com
- web github.com
- web github.com
- web github.com
- web github.com
- web osv.dev
- web github.com
- web github.com