Skip to content

chore(deps): update dependency storybook to v8.6.19 [security] - #456

Open
renovate[bot] wants to merge 1 commit into
mainfrom
renovate/npm-storybook-vulnerability
Open

renovate[bot] wants to merge 1 commit into
mainfrom
renovate/npm-storybook-vulnerability

Conversation

@renovate

@renovate renovate Bot commented Dec 18, 2025 •

Copy link
Copy Markdown
Contributor

Note

This PR body was truncated due to platform limits.

This PR contains the following updates:

Package Change Age Confidence
storybook (source) 8.4.4 → 8.6.19 age confidence

Warning

Some dependencies could not be looked up. Check the warning logs for more information.

@coderabbitai: ignore


Storybook manager bundle may expose environment variables during build

CVE-2025-68429 / GHSA-8452-54wp-rmv6

More information

Details

On December 11th, the Storybook team received a responsible disclosure alerting them to a potential vulnerability in certain built and published Storybooks.

The vulnerability is a bug in how Storybook handles environment variables defined in a .env file, which could, in specific circumstances, lead to those variables being unexpectedly bundled into the artifacts created by the storybook build command. When a built Storybook is published to the web, the bundle’s source is viewable, thus potentially exposing those variables to anyone with access. If those variables contained secrets, they should be considered compromised.

Who is impacted?

For a project to be vulnerable to this issue, it must:

  • Build the Storybook (i.e. run storybook build directly or indirectly) in a directory that contains a .env file (including variants like .env.local)
  • The .env file contains sensitive secrets
  • Use Storybook version 7.0.0 or above
  • Publish the built Storybook to the web

Storybooks built without a .env file at build time are not affected, including common CI-based builds where secrets are provided via platform environment variables rather than .env files.

Users' Storybook runtime environments (i.e. storybook dev) are not affected. Deployed applications that share a repo with a project's Storybook are not affected.

Storybook 6 and below are not affected.

Recommended actions

First, Storybook recommends that everyone audit for any sensitive secrets provided via .env files and rotate those keys.

Second, Storybook has released patched versions of all affected major Storybook versions that no longer have this vulnerability. Projects should upgrade their Storybook—on both local machines and CI environments—to one of these versions before publishing again.

  • 10.1.10+
  • 9.1.17+
  • 8.6.15+
  • 7.6.21+

Finally, some projects may have been relying on the undocumented behavior at the heart of this issue and will need to change how they reference environment variables after this update. If a project can no longer read necessary environmental variable values, it can either prefix the variables with STORYBOOK_ or use the env property in Storybook’s configuration to manually specify values. In either case, do not include sensitive secrets as they will be included in the built bundle.

Further information

Details of the vulnerability can be found on the Storybook announcement.

Severity

  • CVSS Score: 7.3 / 10 (High)
  • Vector String: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:L

References

This data is provided by the GitHub Advisory Database (CC-BY 4.0).


Storybook Dev Server is Vulnerable to WebSocket Hijacking

CVE-2026-27148 / GHSA-mjf5-7g4m-gx5w

More information

Details

Summary

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.

Details

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 a 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, which can be exploited via unauthorized WebSocket connections to achieve persistent XSS or Remote Code Execution (RCE).

Note: recent versions of Chrome have some protections against this, but Firefox does not.

Impact

This vulnerability can lead to supply chain compromise. Key risks include:

  • Remote Code Execution: The vulnerability can allow attackers to execute malicious code, with the extent of impact depending on the configuration. Server-side RCE is possible in non-default configurations, such as when stories are executed via portable stories in JSDOM, potentially allowing attackers to exfiltrate credentials and environment variables, access source code and the filesystem, establish backdoors, or pivot to internal network resources.
  • Persistent XSS: Malicious payloads are written directly into story source files. If the malicious payload is committed to version control, it becomes part of the codebase and can propagate to deployed Storybook documentation sites, affecting developers and stakeholders who view them.
  • Supply Chain Propagation: If the modified source files are committed, injected code can spread to other team members via git, execute in CI/CD pipelines, and affect shared component libraries used across multiple projects.
Affected versions

8.1 and above. While the exploitable functionality was introduced in 8.1, the patch has been applied to 7.x as a precautionary measure given the underlying WebSocket behaviour.

Recommended actions

Update to one of the patched versions: 7.6.23, 8.6.17, 9.1.19, 10.2.10.

Severity

  • CVSS Score: 8.9 / 10 (High)
  • Vector String: CVSS:4.0/AV:N/AC:L/AT:P/PR:N/UI:A/VC:H/VI:H/VA:H/SC:H/SI:H/SA:H

References

This data is provided by the GitHub Advisory Database (CC-BY 4.0).


Storybook dev server vulnerable to code injection from the local network

CVE-2026-114126 / GHSA-px85-f4q5-jh77

More information

Details

Summary: The Storybook dev server exposes its WebSocket authentication token to any client that can load its HTML pages. Any host on a LAN can open a Storybook app by IP address, and therefore obtain the token. The WebSocket can be used to inject code into story files or to create new files. Under the right circumstances, an attacker can execute code on the machine of a developer connected on the same LAN.

Who is impacted?

You are impacted if you run a Storybook dev server whilst connected on an untrusted local network, or to a WiFi access point posing as a trusted network. The impact of this advisory is more important if you have the Vitest addon installed and are using an old version of Vitest.

You are not impacted if:

  • You run a dev server in an environment that other devices on your network cannot reach (e.g. a container that does not publish the Storybook port, or publishes it only on 127.0.0.1)
  • You run a dev server whilst connected to a trusted local network
  • You serve a built version of Storybook on your machine
Recommended actions
Upgrade Storybook

Storybook has released patched versions of all affected major Storybook versions that fix all the vulnerabilities necessary for the worst-case scenario above to occur.

Upgrade to a patched version listed below before running storybook dev again. If you cannot upgrade immediately, do not run an affected Storybook dev server until you can apply the fix.

  • 11.0.0-alpha.6
  • 10.6.2
  • 9.1.21
  • 8.6.19
Review potentially breaking changes

Due to the exceptional nature of the reported vulnerabilities, the Storybook team has decided to change the default behavior of Storybook, including versions 8 and 9, for several network-related features that are not essential to most Storybook users' workflow. If your team relies on the affected features, this document explains how to fall back to the previous behavior.

Storybook now only listens on 127.0.0.1 by default

By default, the Storybook dev server no longer binds to all network interfaces on your machine. It only binds to the loopback address 127.0.0.1. You can still open it at http://localhost:6006. This prevents other devices on the same network from seeing your Storybook server.

To share a Storybook with others, consider publishing it to Chromatic (free). To share it on a LAN without exposing the dev server, build a static Storybook with storybook build and serve the output folder with any static file server.

To share a live Storybook running in dev mode, you can use the --host CLI option to bind to the LAN IP you want to share Storybook on, e.g. storybook dev --host 192.168.0.110. Host and origin validation stays enabled with this option. If you use --host 0.0.0.0 instead, also set core.allowedHosts to the hostnames you will use. Without it, host and origin validation is disabled, and Storybook shows a warning and asks you to confirm before it starts.

Consider using a firewall to restrict incoming packets to known colleague IPs, and avoid using --host on an untrusted WiFi network.

The Vitest addon now disables browser.api.allowWrite and browser.api.allowExec

Storybook no longer allows code running in Vitest Browser mode to write to the developer’s machine or execute other processes. In the unlikely scenario that you rely on this capability in your tests, you can manually re-enable these APIs in your Vitest config.

The saveStoryRequest event validates input more strictly

Storybook strengthened input validation in saveStoryRequest, so addons and the Storybook UI can now only write serialized args and story titles. It is no longer possible to exploit input validation weaknesses to e.g. write play functions with a custom addon.

If you develop an addon that writes or edits files on users’ behalf, reach out to the Storybook team to get advice on security best practice.

Disclosure timeline

On August 19th, the Storybook team received a responsible disclosure showing that the WebSocket token can be stolen by an attacker sharing a LAN with a Storybook dev server.

The disclosure identified several actions an attacker can do. An attacker can bypass input validation to write a payload in a story file.

They can then trigger a test run via the WebSocket. If the Vitest addon is installed, the payload can exploit a Vitest API to write other files, with more exploit logic to the user’s filesystem.

Depending on the exploit content, where the file is written, and what software the developer uses, that exploit could then be executed.

Severity

  • CVSS Score: 8.7 / 10 (High)
  • Vector String: CVSS:4.0/AV:A/AC:L/AT:N/PR:N/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N

References

This data is provided by the GitHub Advisory Database (CC-BY 4.0).


Release Notes

storybookjs/storybook (storybook)

v8.6.19

Compare Source

8.6.19

  • Highlight: Prevent menu items from emitting arbitrary channel events
  • Channels: Restrict preview postMessage to known manager origins
  • Core: Separate manager and preview roles on the dev server channel
  • Core: Block iframe embedding of the dev server from non-localhost origins
  • Core: Reject component search queries outside the project
  • Core: Validate component export name when creating a story
  • Core: Add host validation warning and origin validation for MCP
  • Core: Contain save story path to the project root
  • Core: Validate save story name and arg keys as identifiers
  • Addon Vitest: Disable browser file writes and command execution

v8.6.18

Compare Source

8.6.18

  • Add request validation

v8.6.17

Compare Source

8.6.17

  • Harden websocket connection

v8.6.16

Compare Source

8.6.16

  • No-op release. No changes.

v8.6.15

Compare Source

8.6.15

v8.6.14

Compare Source

v8.6.13

Compare Source

v8.6.12

Compare Source

v8.6.11

Compare Source

v8.6.10

Compare Source

v8.6.9

Compare Source

v8.6.8

Compare Source

v8.6.7

Compare Source

v8.6.6

Compare Source

v8.6.5

Compare Source

v8.6.4

Compare Source

v8.6.3

Compare Source

v8.6.2

Compare Source

v8.6.1

Compare Source

v8.6.0

Compare Source

The 8.6 release focuses on Storybook Test, which brings realtime component, accessibility, and visual UI tests to your favorite component workshop.

Here’s what’s new:

  • 🎁 Storybook Test installer for out-of-the-box tests in new projects
  • 🦾 Accessibility “todo” workflow to systematically fix a11y violations
  • 🗜️ 80% smaller create-storybook package for much faster installs
  • 🧪 Dozens of Test fixes based on user feedback
  • 📕 Docs fixes for table of contents, code snippets, and more
  • 🚨 Key security fixes for Vite and ESbuild
  • 💯 Hundreds more improvements
List of all updates

v8.5.8

Compare Source

v8.5.7

Compare Source

v8.5.6

Compare Source

v8.5.5

Compare Source

v8.5.4

Compare Source

v8.5.3

Compare Source

v8.5.2

Compare Source

v8.5.1

Compare Source

v8.5.0

Compare Source

Storybook 8.5 is packed with powerful features to enhance your development workflow. This release makes it easier than ever to build accessible, well-tested UIs. Here’s what’s new:

  • 🦾 Realtime accessibility tests to help build UIs for everybody
  • 🛡️ Project code coverage to measure the completeness of your tests
  • 🎯 Focused tests for faster test feedback
  • ⚛️ React Native Web Vite framework (experimental) for testing mobile UI⚛️
  • 🎁 Storybook test early access program to level up your testing game
  • 💯 Hundreds more improvements
List of all updates

[!IMPORTANT]
✂ PR body was truncated to here.


Configuration

📅 Schedule: (in timezone Asia/Tokyo)

  • Branch creation
    • At any time (no schedule defined)
  • Automerge
    • At any time (no schedule defined)

🚦 Automerge: Enabled.

♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.

🔕 Ignore: Close this PR and you won't be reminded about this update again.


  • If you want to rebase/retry this PR, check this box

This PR was generated by Mend Renovate. View the repository job log.

@renovate
renovate Bot force-pushed the renovate/npm-storybook-vulnerability branch 2 times, most recently from 3cb7dac to 3a88ec9 Compare December 31, 2025 19:37
@renovate
renovate Bot force-pushed the renovate/npm-storybook-vulnerability branch from 3a88ec9 to 05178f8 Compare February 26, 2026 21:22
@renovate renovate Bot changed the title chore(deps): update dependency storybook to v8.6.15 [security] chore(deps): update dependency storybook to v8.6.17 [security] Feb 26, 2026
@renovate renovate Bot changed the title chore(deps): update dependency storybook to v8.6.17 [security] chore(deps): update dependency storybook to v8.6.17 [security] - autoclosed Mar 27, 2026
@renovate renovate Bot closed this Mar 27, 2026
@renovate
renovate Bot deleted the renovate/npm-storybook-vulnerability branch March 27, 2026 01:40
@renovate renovate Bot changed the title chore(deps): update dependency storybook to v8.6.17 [security] - autoclosed chore(deps): update dependency storybook to v8.6.17 [security] Mar 30, 2026
@renovate renovate Bot reopened this Mar 30, 2026
@renovate
renovate Bot force-pushed the renovate/npm-storybook-vulnerability branch 2 times, most recently from 05178f8 to d5a8bba Compare March 30, 2026 18:34
@renovate renovate Bot changed the title chore(deps): update dependency storybook to v8.6.17 [security] chore(deps): update dependency storybook to v8.6.17 [security] - autoclosed Apr 27, 2026
@renovate renovate Bot closed this Apr 27, 2026
@renovate renovate Bot changed the title chore(deps): update dependency storybook to v8.6.17 [security] - autoclosed chore(deps): update dependency storybook to v8.6.17 [security] Apr 27, 2026
@renovate renovate Bot reopened this Apr 27, 2026
@renovate
renovate Bot force-pushed the renovate/npm-storybook-vulnerability branch 2 times, most recently from d5a8bba to efbe3ad Compare April 27, 2026 21:41
@renovate
renovate Bot force-pushed the renovate/npm-storybook-vulnerability branch from efbe3ad to 62d3c7f Compare October 27, 2026 15:35
@renovate renovate Bot changed the title chore(deps): update dependency storybook to v8.6.17 [security] chore(deps): update dependency storybook to v8.6.19 [security] Oct 27, 2026

This branch has not been deployed

No deployments
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

0 participants