← Back
CVE-2026-32689
Vulnerability in phoenix (CVE-2026-32689)
Summary
vulnerability in phoenix (CVE-2026-32689). Risk of unauthorized operations or information disclosure. Exploitable via ``Origin``. Mitigation: upgrade to `1.8.6` or later.
AI summary snake-internal / snake-material-v2
A vulnerability tracked as **CVE-2026-32689** has been found in phoenix.
Attackers can target a specific entry point like ``Origin`` over the network to misuse the product.
Risk of unauthorized operations or information disclosure. CVSS score: ?/10.
What to do: upgrade phoenix to **1.8.6** or later.
If unsure, ask your IT team or search "phoenix CVE-2026-32689" on the vendor's site.
CVE-2026-32689 (phoenix) — CWE-770 /
Attack surface: `Origin` / `Phoenix.Socket`
Patched: `1.8.6` — 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.
❓ What is the problem
**A vulnerability** (CWE-770) exists in phoenix. Attackers reach the vulnerable code path via ``Origin`` without authentication.
📍 Affected scope
phoenix — . Attack surface: `Origin` / `Phoenix.Socket`.
🔥 Severity
Severity: ?. Risk of unauthorized operations or information disclosure
🔧 How to fix
Update to **1.8.6**.
🛡️ Workaround
Until the patch is applied: disable the affected feature, apply WAF rules, or restrict access via network ACLs.
🔍 Detection
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 (7 steps)
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 し、稼働しているサービス・バージョンを把握する。
-
6Apply patch patch
Upgrade phoenix to 1.8.6ステージング環境で 1.8.6 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスと、Step 3 で見つけた異常検知の続報チェックを含めること。
-
7Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番では Step 3 と同じログクエリでアラート再発が無いか継続監視。
Affected packages
erlang
phoenix
[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"1.8.6"}]}]
References
- web https://github.com/phoenixframework/phoenix/security/advisories/GHSA-628h-q48j-jr6q
- web https://nvd.nist.gov/vuln/detail/CVE-2026-32689
- web https://github.com/phoenixframework/phoenix/commit/1a67c61ff9ce0a7711662ac7354861917a7c80f7
- web https://github.com/phoenixframework/phoenix/commit/912ea181fd247c21dbcc49fb97d0053b947d81bf
- web https://cna.erlef.org/cves/CVE-2026-32689.html
- web https://osv.dev/vulnerability/EEF-CVE-2026-32689
- web https://github.com/advisories/GHSA-628h-q48j-jr6q