Skip to content

Conversation

@renovate
Copy link

@renovate renovate bot commented Dec 19, 2025

This PR contains the following updates:

Package Change Age Confidence
storybook (source) 7.5.27.6.21 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)

v7.6.21

Compare Source

v7.6.20

Compare Source

v7.6.19

Compare Source

7.6.19
  • Fix bad release of 7.6.18 containing wrong dependency identifiers, thanks @​jreinhold!

v7.6.18

Compare Source

7.6.18

v7.6.17

Compare Source

v7.6.16

Compare Source

v7.6.15

Compare Source

This release accidentally didn't contain anything.

v7.6.14

Compare Source

v7.6.13

Compare Source

v7.6.12

Compare Source

v7.6.11

Compare Source

v7.6.10

Compare Source

v7.6.9

Compare Source

v7.6.8

Compare Source

v7.6.7

Compare Source

v7.6.6

Compare Source

v7.6.5

Compare Source

v7.6.4

Compare Source

v7.6.3

Compare Source

v7.6.2

Compare Source

v7.6.1

Compare Source

v7.6.0

Compare Source

Storybook 7.6 is here with increased performance and much more!

  • 🔥 Improved SWC support
  • 🧪 New test utilities and fast build mode
  • 🔼 NextJS SWC + avif support & fixes
  • 🤡 SvelteKit page and navigation mocking
  • ⚛️ React-docgen upgrade
  • 🎨 Controls a11y, background theming, and viewports
  • 🩺 CLI: The doctor is in!
  • 🚫 Addons: Remove React as a peer dependency
  • 🪦 Storyshots and Vue2 deprecated
List of all updates

v7.5.3

Compare Source

7.5.3

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 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 was generated by Mend Renovate. View the repository job log.

@codecov
Copy link

codecov bot commented Dec 19, 2025

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 21.44%. Comparing base (703e022) to head (b0a2a19).
⚠️ Report is 1 commits behind head on main.

Additional details and impacted files

Impacted file tree graph

@@             Coverage Diff             @@
##             main     #116       +/-   ##
===========================================
- Coverage   23.80%   21.44%    -2.37%     
===========================================
  Files        1587     1500       -87     
  Lines      170092    68491   -101601     
  Branches     2801     9421     +6620     
===========================================
- Hits        40486    14685    -25801     
+ Misses     128439    52617    -75822     
- Partials     1167     1189       +22     
Flag Coverage Δ
web 8.97% <ø> (-12.53%) ⬇️
web-beta 8.97% <ø> (-12.53%) ⬇️
web-classic 8.97% <ø> (-12.53%) ⬇️
web-utils 8.97% <ø> (-12.53%) ⬇️

Flags with carried forward coverage won't be shown. Click here to find out more.
see 1196 files with indirect coverage changes

🚀 New features to boost your workflow:
  • ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.
  • 📦 JS Bundle Analysis: Save yourself from yourself by tracking and limiting bundle sizes in JS merges.

@renovate renovate bot force-pushed the renovate/npm-storybook-vulnerability branch from b0a2a19 to 9945646 Compare December 24, 2025 05:58
@renovate renovate bot force-pushed the renovate/npm-storybook-vulnerability branch from 9945646 to c5e9d97 Compare January 7, 2026 04:49
@renovate renovate bot force-pushed the renovate/npm-storybook-vulnerability branch from c5e9d97 to b3577cf Compare January 8, 2026 01:01
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.

1 participant