Skip to content
Threat Brief

← All advisories

CVE-2026-8467

Critical 9.5No known exploitationFix available

Unauthenticated remote code execution via HEEx template injection in phoenix_storybook playground

Record last updated

CVSS score

9.5

Critical on a 0 to 10 scale

EPSS, chance of exploitation in 30 days

2.1%

Higher than 82% of scored CVEs. A prediction, not evidence.

CISA remediation deadline

None

Not in the KEV catalog

Description

Code Injection vulnerability in phenixdigital phoenix_storybook allows unauthenticated remote code execution via HEEx template injection in the component playground. A client can send attribute values over the playground WebSocket. A value that closes the attribute quote and adds a HEEx expression is evaluated as Elixir code on the server. PhoenixStorybook.Story.PlaygroundPreviewLive.handle_event/3 accepts attribute names and values from the client and stores them through PhoenixStorybook.ExtraAssignsHelpers.handle_set_variation_assign/3. PhoenixStorybook.Rendering.ComponentRenderer.attributes_markup/1 interpolates string values into a HEEx template without escaping. The template is compiled with EEx.compile_string/2 and evaluated. Releases published as phx_live_storybook have the same code in the PhxLiveStorybook namespace, where the first client entry point is PhxLiveStorybook.Entry.Playground.handle_event/3. This issue affects phoenix_storybook: from 0.5.0 before 1.1.0; phx_live_storybook: from 0.3.0 onward.

Weakness: CWE-94

Patching and mitigation

Patch status
Fix available (source: CVE record (EEF))
Fix documented (source date)
Mitigation
None documented
Vendor guidance
github.com (opens in a new tab)

Affected products

VendorProductAffected versionsFixed inPer
phenixdigitalphoenix_storybookfrom 0.5.0 before 1.1.01.1.0CVE Program
phenixdigitalphoenix_storybookfrom e35379dfe2ef1a71b141899e36f431017c55265d before 56ab8464d4375fa52db806148a06cce126ad481d56ab8464d4375fa52db806148a06cce126ad481dCVE Program
phenixdigitalphoenix_storybook0.3.0Not documentedCVE Program

Timeline

  1. Disclosure

    CVE record published by EEF

    Source: CVE Program (opens in a new tab)

  2. Patch

    Fix documented by CVE record (EEF)

    Source: CVE record (EEF) (opens in a new tab)

Vendor guidance and references