Skip to content

Update dependency storybook to v8.6.17 [SECURITY]#5539

Open
openverse-bot wants to merge 1 commit intomainfrom
gha-renovatenpm-storybook-vulnerability
Open

Update dependency storybook to v8.6.17 [SECURITY]#5539
openverse-bot wants to merge 1 commit intomainfrom
gha-renovatenpm-storybook-vulnerability

Conversation

@openverse-bot
Copy link
Copy Markdown
Collaborator

@openverse-bot openverse-bot commented Dec 18, 2025

This PR contains the following updates:

Package Type Update Change
storybook (source) devDependencies minor 8.4.7 -> 8.6.17

GitHub Vulnerability Alerts

CVE-2025-68429

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.

CVE-2026-27148

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.


Release Notes

storybookjs/storybook (storybook)

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

Configuration

📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).

🚦 Automerge: Enabled.

Rebasing: Whenever PR is behind base branch, 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 has been generated by Renovate Bot.

@openverse-bot openverse-bot requested a review from a team as a code owner December 18, 2025 19:10
@openverse-bot openverse-bot added dependencies Pull requests that update a dependency file 💻 aspect: code Concerns the software code in the repository 🟨 tech: javascript Involves JavaScript 🟩 priority: low Low priority and doesn't need to be rushed 🧰 goal: internal improvement Improvement that benefits maintainers, not users 🧱 stack: frontend Related to the Nuxt frontend labels Dec 18, 2025
@openverse-bot openverse-bot moved this to 👀 Needs Review in Openverse PRs Dec 18, 2025
@github-actions
Copy link
Copy Markdown

github-actions bot commented Dec 18, 2025

Latest k6 run output1

     ✓ status was 200

     checks.........................: 100.00% ✓ 416      ✗ 0   
     data_received..................: 100 MB  416 kB/s
     data_sent......................: 132 kB  548 B/s
     http_req_blocked...............: avg=97.41µs  min=2.32µs   med=4.71µs   max=1.99ms   p(90)=156.89µs p(95)=739.3µs 
     http_req_connecting............: avg=55.67µs  min=0s       med=0s       max=1.93ms   p(90)=99.17µs  p(95)=257.26µs
     http_req_duration..............: avg=158.56ms min=17.94ms  med=105.68ms max=892.14ms p(90)=369.41ms p(95)=437.63ms
       { expected_response:true }...: avg=158.56ms min=17.94ms  med=105.68ms max=892.14ms p(90)=369.41ms p(95)=437.63ms
   ✓ http_req_failed................: 0.00%   ✓ 0        ✗ 416 
     http_req_receiving.............: avg=181.67µs min=53.63µs  med=143.21µs max=4.04ms   p(90)=257.85µs p(95)=303.48µs
     http_req_sending...............: avg=31.39µs  min=7.78µs   med=23.67µs  max=212.47µs p(90)=50.46µs  p(95)=97.17µs 
     http_req_tls_handshaking.......: avg=0s       min=0s       med=0s       max=0s       p(90)=0s       p(95)=0s      
     http_req_waiting...............: avg=158.34ms min=17.81ms  med=105.5ms  max=891.94ms p(90)=369.17ms p(95)=437.32ms
     http_reqs......................: 416     1.725627/s
     iteration_duration.............: avg=852.64ms min=248.46ms med=890.51ms max=1.82s    p(90)=1.16s    p(95)=1.21s   
     iterations.....................: 78      0.323555/s
     vus............................: 3       min=0      max=6 
     vus_max........................: 60      min=60     max=60

Footnotes

  1. This comment will automatically update with new output each time k6 runs for this PR

@openverse-bot openverse-bot force-pushed the gha-renovatenpm-storybook-vulnerability branch from 32cfdb7 to 074018c Compare February 9, 2026 19:02
@openverse-bot openverse-bot force-pushed the gha-renovatenpm-storybook-vulnerability branch from 074018c to 4347a4e Compare February 17, 2026 20:51
@openverse-bot openverse-bot force-pushed the gha-renovatenpm-storybook-vulnerability branch from 4347a4e to dca31d0 Compare February 26, 2026 19:50
@openverse-bot openverse-bot changed the title Update dependency storybook to v8.6.15 [SECURITY] Update dependency storybook to v8.6.17 [SECURITY] Feb 26, 2026
@openverse-bot openverse-bot force-pushed the gha-renovatenpm-storybook-vulnerability branch 2 times, most recently from aa39418 to 24b092e Compare March 3, 2026 19:23
@openverse-bot openverse-bot changed the title Update dependency storybook to v8.6.17 [SECURITY] Update dependency storybook to v8.6.17 [SECURITY] - autoclosed Mar 27, 2026
@github-project-automation github-project-automation bot moved this from 👀 Needs Review to 🚫 Closed in Openverse PRs Mar 27, 2026
@openverse-bot openverse-bot deleted the gha-renovatenpm-storybook-vulnerability branch March 27, 2026 00:43
@openverse-bot openverse-bot changed the title Update dependency storybook to v8.6.17 [SECURITY] - autoclosed Update dependency storybook to v8.6.17 [SECURITY] Mar 30, 2026
@openverse-bot openverse-bot reopened this Mar 30, 2026
@openverse-bot openverse-bot force-pushed the gha-renovatenpm-storybook-vulnerability branch from d822070 to 24b092e Compare March 30, 2026 17:52
@openverse-bot openverse-bot moved this from 🚫 Closed to 👀 Needs Review in Openverse PRs Mar 30, 2026
@openverse-bot openverse-bot force-pushed the gha-renovatenpm-storybook-vulnerability branch from 24b092e to ab8ff57 Compare April 8, 2026 00:45
@openverse-bot openverse-bot force-pushed the gha-renovatenpm-storybook-vulnerability branch from ab8ff57 to 1eda56c Compare April 8, 2026 17:32
@github-actions
Copy link
Copy Markdown

github-actions bot commented Apr 8, 2026

Playwright failure test results: https://github.com/WordPress/openverse/actions/runs/24149414322

It looks like some of the Playwright tests failed. If you made changes to the frontend UI without updating snapshots, this might be the cause. You can download zipped patches containing the updated snapshots alongside a general trace of the tests under the "Artifacts" section in the above page. They're named in the form *_snapshot_diff and *_test_results respectively.

You can read more on how to use these artifacts in the docs.

If the test is flaky, follow the flaky test triage procedure.

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

Labels

💻 aspect: code Concerns the software code in the repository dependencies Pull requests that update a dependency file 🧰 goal: internal improvement Improvement that benefits maintainers, not users 🟩 priority: low Low priority and doesn't need to be rushed 🧱 stack: frontend Related to the Nuxt frontend 🟨 tech: javascript Involves JavaScript

Projects

Status: 👀 Needs Review

Development

Successfully merging this pull request may close these issues.

1 participant