Skip to content

chore(deps): update dependency storybook to v7.6.21 [security]#4687

Merged
renovate[bot] merged 1 commit intomainfrom
renovate/npm-storybook-vulnerability
Jan 12, 2026
Merged

chore(deps): update dependency storybook to v7.6.21 [security]#4687
renovate[bot] merged 1 commit intomainfrom
renovate/npm-storybook-vulnerability

Conversation

@renovate
Copy link
Contributor

@renovate renovate bot commented Dec 18, 2025

This PR contains the following updates:

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


Configuration

📅 Schedule: Branch creation - "" (UTC), 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 was generated by Mend Renovate. View the repository job log.

@renovate renovate bot added dependencies Pull requests that update a dependency file renovate PR created by RenovateBot labels Dec 18, 2025
@renovate renovate bot requested a review from gusevda as a code owner December 18, 2025 22:59
@renovate renovate bot added the dependencies Pull requests that update a dependency file label Dec 18, 2025
@renovate renovate bot enabled auto-merge (squash) December 18, 2025 23:00
@renovate renovate bot added the renovate PR created by RenovateBot label Dec 18, 2025
@renovate renovate bot force-pushed the renovate/npm-storybook-vulnerability branch 2 times, most recently from 67fb25b to 68bab9f Compare January 6, 2026 15:30
@renovate renovate bot changed the title Update dependency storybook to v7.6.21 [SECURITY] chore(deps): update dependency storybook to v7.6.21 [security] Jan 6, 2026
@renovate renovate bot force-pushed the renovate/npm-storybook-vulnerability branch 2 times, most recently from f4bddef to 03a58e4 Compare January 7, 2026 10:57
@renovate renovate bot force-pushed the renovate/npm-storybook-vulnerability branch from 03a58e4 to aeb8a6f Compare January 12, 2026 07:49
@renovate renovate bot merged commit c545324 into main Jan 12, 2026
14 checks passed
@renovate renovate bot deleted the renovate/npm-storybook-vulnerability branch January 12, 2026 07:58
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

dependencies Pull requests that update a dependency file renovate PR created by RenovateBot

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant