Skip to content

Comments

chore(deps): update dependency storybook to v9.1.17 [security]#59

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

chore(deps): update dependency storybook to v9.1.17 [security]#59
renovate[bot] wants to merge 1 commit intomainfrom
renovate/npm-storybook-vulnerability

Conversation

@renovate
Copy link
Contributor

@renovate renovate bot commented Dec 19, 2025

This PR contains the following updates:

Package Change Age Confidence
storybook (source) 9.0.189.1.17 age confidence

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.


Release Notes

storybookjs/storybook (storybook)

v9.1.17

Compare Source

v9.1.16

Compare Source

v9.1.15

Compare Source

v9.1.14

Compare Source

v9.1.13

Compare Source

v9.1.12

Compare Source

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

v9.1.11

Compare Source

v9.1.10

Compare Source

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

v9.1.7

Compare Source

v9.1.6

Compare Source

v9.1.5

Compare Source

v9.1.4

Compare Source

v9.1.3

Compare Source

v9.1.2

Compare Source

v9.1.1

Compare Source

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

v9.1.0

Compare Source

Storybook 9.1 is packed with new features and improvements to enhance accessibility, streamline testing, and make your development workflow even smoother!

🚀 Improved upgrade command with monorepo support for seamless upgrades
🅰 Angular fixes for Tailwind 4, cache busting, and zoneless compatibility
🧪 sb.mock API and Automocking: one-line module mocking to simplify your testing workflow
🧪 Favicon shows test run status for quick visual feedback
⚛️ Easier configuration for React Native projects
🔥 Auto-abort play functions on HMR to avoid unwanted side effects
🏗️ Improved CSF factories API for type safe story definitions
♿️ A11y improvements across Storybook’s UI — addon panel, toolbar, sidebar, mobile & more
💯 Dozens more fixes and improvements based on community feedback!

List of all updates

Configuration

📅 Schedule: Branch creation - "" (UTC), 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.

@renovate renovate bot force-pushed the renovate/npm-storybook-vulnerability branch from c54c1a8 to 6cf695a Compare December 22, 2025 12:24
@renovate renovate bot force-pushed the renovate/npm-storybook-vulnerability branch from 6cf695a to 8749fc2 Compare January 1, 2026 12:09
@renovate renovate bot force-pushed the renovate/npm-storybook-vulnerability branch 2 times, most recently from 484523f to fd97c62 Compare January 14, 2026 01:11
@renovate renovate bot force-pushed the renovate/npm-storybook-vulnerability branch 2 times, most recently from d89b29e to 7bdc3a9 Compare January 24, 2026 03:59
@renovate renovate bot force-pushed the renovate/npm-storybook-vulnerability branch from 7bdc3a9 to a4538f6 Compare February 3, 2026 23:14
@renovate renovate bot force-pushed the renovate/npm-storybook-vulnerability branch from a4538f6 to 216957a Compare February 11, 2026 20:55
@renovate renovate bot force-pushed the renovate/npm-storybook-vulnerability branch from 216957a to 297f5b8 Compare February 18, 2026 07:53
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

0 participants