Storybook Dev Server Vulnerable to WebSocket Hijacking

Summary

Storybook is a frontend workshop for building user interface components and pages in isolation. Prior to versions 7.6.23, 8.6.17, 9.1.19, and 10.2.10, the WebSocket functionality in Storybook's dev server, used to create and update stories, is vulnerable to WebSocket hijacking. This vulnerability only affects the Storybook dev server; production builds are not impacted. Exploitation requires a developer to visit a malicious website while their local Storybook dev server is running. Because the WebSocket connection does not validate the origin of incoming connections, a malicious site can silently send WebSocket messages to the local instance without any further user interaction. If the Storybook dev server is intentionally exposed publicly (e.g. for design reviews or stakeholder demos) the risk is higher, as no malicious site visit is required. Any unauthenticated attacker can send WebSocket messages to it directly. The vulnerability affects the WebSocket message handlers for creating and saving stories. Both are vulnerable to injection via unsanitized input in the componentFilePath field, which can be exploited to achieve persistent XSS or Remote Code Execution (RCE). Versions 7.6.23, 8.6.17, 9.1.19, and 10.2.10 contain a fix for the issue.

Timeline

1. Feb 25, 2026, 9:46 PM UTCCVE published
2. Feb 26, 2026, 8:25 PM UTCCISA SSVC assessment

   Exploitation: none · Automatable: no · Technical impact: total

3. Jul 15, 2026, 1:14 AM UTCRecord last updated

Affected versions

• storybookjs storybook

  fixed in 7.6.23; From 8.1.0 · fixed in 8.6.17; From 9.0.0 · fixed in 9.1.19; From 10.0.0 · fixed in 10.2.10

• storybooknpm

  From 8.1.0 · fixed in 8.6.17

• storybooknpm

  From 8.7.0-alpha.0 · fixed in 9.1.19

• storybooknpm

  From 10.0.0-beta.0 · fixed in 10.2.10

References 9