chore(deps): update dependency storybook to v8.6.17 [security]#2739
chore(deps): update dependency storybook to v8.6.17 [security]#2739renovate[bot] wants to merge 1 commit intomainfrom
Conversation
|
|
Important Review skippedBot user detected. To trigger a single review, invoke the You can disable this status message by setting the Comment |
Codecov Report✅ All modified and coverable lines are covered by tests. Additional details and impacted files@@ Coverage Diff @@
## main #2739 +/- ##
=======================================
Coverage 81.80% 81.80%
=======================================
Files 149 149
Lines 2957 2957
Branches 934 934
=======================================
Hits 2419 2419
- Misses 504 534 +30
+ Partials 34 4 -30 ☔ View full report in Codecov by Sentry. 🚀 New features to boost your workflow:
|
22516b5 to
6a76001
Compare
05421a5 to
21b03e0
Compare
21b03e0 to
1ba1a6a
Compare
1ba1a6a to
31d938e
Compare
05c80a7 to
7a88256
Compare
7a88256 to
601370d
Compare
This PR contains the following updates:
8.4.7→8.6.17GitHub 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
.envfile, which could, in specific circumstances, lead to those variables being unexpectedly bundled into the artifacts created by thestorybook buildcommand. 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:
storybook builddirectly or indirectly) in a directory that contains a.envfile (including variants like.env.local).envfile contains sensitive secrets7.0.0or aboveStorybooks built without a
.envfile at build time are not affected, including common CI-based builds where secrets are provided via platform environment variables rather than.envfiles.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
.envfiles 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 theenvproperty 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:
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.17Compare Source
8.6.17
v8.6.16Compare Source
8.6.16
v8.6.15Compare Source
v8.6.14Compare Source
v8.6.13Compare Source
react-native-web- #31324, thanks @ndelangen!v8.6.12Compare Source
ember-template-compilerimport for ember 6+ - #30682, thanks @leoeuclids!node_modulesfrom docgen - #30981, thanks @JReinhold!v8.6.11Compare Source
v8.6.10Compare Source
v8.6.9Compare Source
v8.6.8Compare Source
v8.6.7Compare Source
v8.6.6Compare Source
v8.6.5Compare Source
@angular-devkit/build-angularto installed packages - #30790, thanks @kasperpeulen!svelte2tsx@0.7.35- #30784, thanks @JReinhold!crypto.randomUUID- #30781, thanks @JReinhold!v8.6.4Compare Source
node_modulesin stats file - #30711, thanks @JReinhold!v8.6.3Compare Source
v8.6.2Compare Source
v8.6.1Compare Source
v8.6.0Compare 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:
List of all updates
--yesand fix--features- #30534, thanks @ghengeveld!UniversalStoreAPI to sync state/events between multiple environments - #30445, thanks @JReinhold!node_modules- #30643, thanks @ndelangen!addon-essentialsnot working when used withgetAbsolutePath- #30557, thanks @JReinhold!+page.sveltefiles - #30369, thanks @xeho91!vitest.config.tswith workspaces, otherwise createvitest.workspace.ts- #30583, thanks @ghengeveld!v8.5.8Compare Source
esbuild@^0.25- #30574, thanks @JReinhold!v8.5.7Compare Source
v8.5.6Compare Source
v8.5.5Compare Source
v8.5.4Compare Source
v8.5.3Compare Source
globalstoextract()- #30415, thanks @ndelangen!v8.5.2Compare Source
v8.5.1Compare Source
interaction test->component test- #30333, thanks @kylegach!v8.5.0Compare 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:
List of all updates
@vitest/coverage-v8during postinstall if no coverage reporter is installed - #29993, thanks @ghengeveld!vitestdetects missing deps - #29763, thanks @ndelangen!test.includepatterns - #30029, thanks @JReinhold!vitestcrashes - #29751, thanks @ndelangen!vitest.setup.js- #30233, thanks @JReinhold!experimental-nextjs-vite- #29814, thanks @ndelangen!globwithtinyglobby- #29817, thanks @ghengeveld!staticDirswith Vitest - #29811, thanks @ghengeveld!require.resolve- #30026, thanks @ndelangen!storybookcommand - #29480, thanks @toothlessdev!TESTING_MODULE_RUN_ALL_REQUESTfor backward compatibility - #29711, thanks @ghengeveld!ERR_PACKAGE_PATH_NOT_EXPORTEDin@storybook/node-logger- #30093, thanks @JReinhold!scrollIntoViewbehavior and reimplement testing module time rendering - #30044, thanks @ghengeveld!@types/nodetodevDepsconsistently - #30163, thanks @ndelangen!useSharedState- #30259, thanks @JReinhold!react-confettiwith@neoconfetti/react- #30098, thanks @ndelangen!@storybook/testas optional peer dependency - #29754, thanks @yannbf!Configuration
📅 Schedule: Branch creation - "" in timezone Asia/Seoul, Automerge - At any time (no schedule defined).
🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.
♻ 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.
This PR was generated by Mend Renovate. View the repository job log.