chore(deps): update devdependency storybook to v9.1.19 [security]

[renovate]

This PR contains the following updates:

Package	Change	Age	Confidence
storybook (source)	9.1.2 → 9.1.19

---

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

• https://github.com/storybookjs/storybook/security/advisories/GHSA-8452-54wp-rmv6
• https://nvd.nist.gov/vuln/detail/CVE-2025-68429
• https://storybook.js.org/blog/security-advisory
• https://github.com/advisories/GHSA-8452-54wp-rmv6

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

• https://github.com/storybookjs/storybook/security/advisories/GHSA-mjf5-7g4m-gx5w
• https://nvd.nist.gov/vuln/detail/CVE-2026-27148
• https://github.com/storybookjs/storybook/commit/0affdf928bd6fafbadfb1dfe22ce6104805e10e8
• https://github.com/storybookjs/storybook/commit/54689a8add18ea75d628c540f4bc677592a1e685
• https://github.com/storybookjs/storybook/commit/b8cfa77c73940c140acdcd8a06ab1ea913c44761
• https://github.com/storybookjs/storybook/commit/d34085f39c647f5c23c3a3b2d197c18602fcf876
• https://github.com/storybookjs/storybook/releases/tag/v10.2.10
• https://github.com/storybookjs/storybook/releases/tag/v7.6.23
• https://github.com/storybookjs/storybook/releases/tag/v8.6.17
• https://github.com/storybookjs/storybook/releases/tag/v9.1.19
• https://github.com/advisories/GHSA-mjf5-7g4m-gx5w

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

---

Release Notes

storybookjs/storybook (storybook)

v9.1.19

Compare Source

9.1.19

• Harden websocket connection

v9.1.18

Compare Source

9.1.18

• No-op release. No changes.

v9.1.17

Compare Source

9.1.17

• Core: Fix .env-file parsing, thanks @​jreinhold!

v9.1.16

Compare Source

• CLI: Fix Nextjs project creation in empty directories - #​32828, thanks @​yannbf!
• Core: Add experimental_devServer preset - #​32862, thanks @​yannbf!
• Telemetry: Fix preview-first-load event - #​32859, thanks @​shilman!

v9.1.15

Compare Source

• Core: Add preview-first-load telemetry - #​32770, thanks @​shilman!
• Dependencies: Update vite-plugin-storybook-nextjs - #​32821, thanks @​ndelangen!

v9.1.14

Compare Source

• NextJS: Add NextJS 16 support - #​32791, thanks @​yannbf and @​ndelangen!
• Addon-Vitest: Support Vitest 4 - #​32819, thanks @​yannbf and @​ndelangen!
• CSF: Fix play-fn tag for methods - #​32695, thanks @​shilman!

v9.1.13

Compare Source

• Nextjs: Fix config access for Vite - #​32759, thanks @​valentinpalkovic!

v9.1.12

Compare Source

• Maintenance: Hotfix for missing nextjs dts files, thanks @​ndelangen!

v9.1.11

Compare Source

• Automigration: Improve the viewport/backgrounds automigration - #​32619, thanks @​valentinpalkovic!
• Mocking: Fix sb.mock usage in Storybook's deployed in subpaths - #​32678, thanks @​valentinpalkovic!
• NextJS-Vite: Automatically fix bad PostCSS configuration - #​32691, thanks @​ndelangen!
• React Native Web: Fix REACT_NATIVE_AND_RNW should detect vite builder - #​32718, thanks @​dannyhw!
• Telemetry: Add metadata for react routers - #​32615, thanks @​shilman!

v9.1.10

Compare Source

• Automigrations: Add automigration for viewport and backgrounds - #​31614, thanks @​valentinpalkovic!
• Telemetry: Log userAgent in onboarding - #​32566, thanks @​shilman!

v9.1.9

Compare Source

• Angular: Enable experimental zoneless detection on Angular v21 - #​32580, thanks @​yannbf!
• Svelte: Ignore inherited HTMLAttributes docgen when using utility types - #​32173, thanks @​steciuk!

v9.1.8

Compare Source

• PreactVite: Add node entry point - #​32534, thanks @​ndelangen!

v9.1.7

Compare Source

• Dependencies: Update vite-plugin-storybook-nextjs to 2.0.7 - #​32331, thanks @​k35o!
• React: Preserve @ts-expect-error in preview - #​32442, thanks @​mrginglymus!
• Telemetry: Queue error reporting & filter browser-extention - #​32499, thanks @​ndelangen!

v9.1.6

Compare Source

• CLI: Capture the version specifier used in create-storybook - #​32344, thanks @​shilman!
• Instrumenter: Fix userEvent.type performance regression - #​32439, thanks @​ndelangen!
• React Native Web: Fix RNW peer dependency version - #​32438, thanks @​dannyhw!
• Telemetry: Record known CLI integrations - #​32448, thanks @​shilman!

v9.1.5

Compare Source

• CSF: Support satisfies x as y syntax - #​32169, thanks @​diagramatics!
• Vitest addon: Handle Playwright installation errors gracefully - #​32329, thanks @​ndelangen!

v9.1.4

Compare Source

• Angular: Properly merge builder options and browserTarget options - #​32272, thanks @​kroeder!
• Core: Optimize bundlesize, by reusing internal/babel in mocking-utils - #​32350, thanks @​ndelangen!
• Svelte & Vue: Add framework-specific docgen option to disable docgen processing - #​32319, thanks @​copilot-swe-agent!
• Svelte: Support @sveltejs/vite-plugin-svelte v6 - #​32320, thanks @​JReinhold!

v9.1.3

Compare Source

• Docs: Move button in ArgsTable heading to fix screenreader announcements - #​32238, thanks @​Sidnioulz!
• Mock: Catch errors when transforming preview files - #​32216, thanks @​valentinpalkovic!
• Next.js: Fix version mismatch error in Webpack - #​32306, thanks @​valentinpalkovic!
• Telemetry: Disambiguate traffic coming from error/upgrade links - #​32287, thanks @​shilman!
• Telemetry: Disambiguate unattributed traffic from Onboarding - #​32286, thanks @​shilman!

---

Configuration

📅 Schedule: (UTC)

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

🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

♻ 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.

[netlify]

✅ Deploy Preview for stuartc ready!

Name	Link
🔨 Latest commit	7fa730c
🔍 Latest deploy log	https://app.netlify.com/projects/stuartc/deploys/6a54cb682934d00008cc9b71
😎 Deploy Preview	https://deploy-preview-122--stuartc.netlify.app
📱 Preview on mobile	Toggle QR Code... Use your smartphone camera to open QR code link.
🤖 Make changes	Run an agent on this branch

---

To edit notification comments on pull requests, go to your Netlify project configuration.

[Decipher]

Superseded by #135, which consolidates this with the other already-passing dependency bumps and retargets develop per GitFlow.

[renovate]

Renovate Ignore Notification

Because you closed this PR without merging, Renovate will ignore this update (9.1.19). You will get a PR once a newer version is released. To ignore this dependency forever, add it to the ignoreDeps array of your Renovate config.

If you accidentally closed this PR, or if you changed your mind: rename this PR to get a fresh replacement PR.