← Back
CVE-2026-8467
Code Injection in phoenix_storybook (CVE-2026-8467)
Summary
code injection in phoenix_storybook (CVE-2026-8467). Risk of unauthorized operations or information disclosure. Exploitable via ``Kernel``. Mitigation: upgrade to `1.1.0` or later.
AI summary snake-internal / snake-material-v2
A vulnerability tracked as **CVE-2026-8467** has been found in phoenix_storybook.
Attackers can target a specific entry point like ``Kernel`` over the network to misuse the product.
Risk of unauthorized operations or information disclosure. CVSS score: ?/10.
What to do: upgrade phoenix_storybook to **1.1.0** or later.
If unsure, ask your IT team or search "phoenix_storybook CVE-2026-8467" on the vendor's site.
CVE-2026-8467 (phoenix_storybook) — CWE-94 /
Attack surface: `Kernel` / `extra_assigns_helpers.ex` / `component_renderer.ex` / `EXPR`
Patched: `1.1.0` — 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
**arbitrary code execution** (CWE-94) exists in phoenix_storybook. Attackers reach the vulnerable code path via ``Kernel`` without authentication.
📍 Affected scope
phoenix_storybook — . Attack surface: `Kernel` / `extra_assigns_helpers.ex` / `component_renderer.ex` / `EXPR`.
🔥 Severity
Severity: ?. Risk of unauthorized operations or information disclosure
🔧 How to fix
Update to **1.1.0**.
🛡️ 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_storybook' .` 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_storybook' . | grep -v node_modulesリポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で `phoenix_storybook` を grep し、稼働しているサービス・バージョンを把握する。
-
6Apply patch patch
Upgrade phoenix_storybook to 1.1.0ステージング環境で 1.1.0 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスと、Step 3 で見つけた異常検知の続報チェックを含めること。
-
7Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番では Step 3 と同じログクエリでアラート再発が無いか継続監視。
Affected packages
Hex
phoenix_storybook
[{"type":"SEMVER","events":[{"introduced":"0.5.0"},{"fixed":"1.1.0"}]}]
erlang
phoenix_storybook
[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"1.1.0"}]}]
References
- advisory https://nvd.nist.gov/vuln/detail/CVE-2026-8467
- package https://hex.pm/packages/phoenix_storybook
- package https://github.com/phenixdigital/phoenix_storybook
- web https://cna.erlef.org/cves/CVE-2026-8467.html
- web https://github.com/phenixdigital/phoenix_storybook/commit/56ab8464d4375fa52db806148a06cce126ad481d
- web https://github.com/phenixdigital/phoenix_storybook/security/advisories/GHSA-55hg-8qxv-qj4p
- web https://osv.dev/vulnerability/EEF-CVE-2026-8467
- web https://github.com/advisories/GHSA-55hg-8qxv-qj4p