Skip to content

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

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

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

Conversation

@renovate
Copy link
Copy Markdown

@renovate renovate bot commented Dec 30, 2025

This PR contains the following updates:

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


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

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


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

v7.5.2

Compare Source

v7.5.1

Compare Source

v7.5.0

Compare Source

Storybook 7.5 enhances your Storybook experience with several key updates:

  • 💃🏼 Now supports Lit 3.0 and Vite 5
  • 👻 storiesOf and storyStoreV6 officially deprecated
  • 🔨 Fix Webpack5 build errors not being propagated
  • 🀄 Support rename font import for Next.js
  • ⬆️ Upgrade react-docgen to 6.0.x and improve argTypes
  • ✨ Many Angular improvements such as introducing argsToTemplate , new schema debugging options, support for standalone directives, etc.
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.

@vercel
Copy link
Copy Markdown

vercel bot commented Dec 30, 2025

The latest updates on your projects. Learn more about Vercel for GitHub.

Project Deployment Actions Updated (UTC)
hygraph-next-enterprise Ready Ready Preview, Comment Mar 31, 2026 9:43am

Request Review

@github-actions
Copy link
Copy Markdown

Seems you are using me but didn't get OPENAI_API_KEY seted in Variables/Secrets for this repo. you could follow readme for more information

@github-actions
Copy link
Copy Markdown

github-actions bot commented Jan 8, 2026

Seems you are using me but didn't get OPENAI_API_KEY seted in Variables/Secrets for this repo. you could follow readme for more information

@github-actions
Copy link
Copy Markdown

Seems you are using me but didn't get OPENAI_API_KEY seted in Variables/Secrets for this repo. you could follow readme for more information

@github-actions
Copy link
Copy Markdown

Seems you are using me but didn't get OPENAI_API_KEY seted in Variables/Secrets for this repo. you could follow readme for more information

@github-actions
Copy link
Copy Markdown

Seems you are using me but didn't get OPENAI_API_KEY seted in Variables/Secrets for this repo. you could follow readme for more information

@github-actions
Copy link
Copy Markdown

Seems you are using me but didn't get OPENAI_API_KEY seted in Variables/Secrets for this repo. you could follow readme for more information

@github-actions
Copy link
Copy Markdown

Seems you are using me but didn't get OPENAI_API_KEY seted in Variables/Secrets for this repo. you could follow readme for more information

@github-actions
Copy link
Copy Markdown

Seems you are using me but didn't get OPENAI_API_KEY seted in Variables/Secrets for this repo. you could follow readme for more information

@github-actions
Copy link
Copy Markdown

Seems you are using me but didn't get OPENAI_API_KEY seted in Variables/Secrets for this repo. you could follow readme for more information

@github-actions
Copy link
Copy Markdown

github-actions bot commented Mar 5, 2026

Seems you are using me but didn't get OPENAI_API_KEY seted in Variables/Secrets for this repo. you could follow readme for more information

@github-actions
Copy link
Copy Markdown

Seems you are using me but didn't get OPENAI_API_KEY seted in Variables/Secrets for this repo. you could follow readme for more information

@renovate renovate bot force-pushed the renovate/npm-storybook-vulnerability branch from 02f7ae0 to 7d16d3a Compare March 31, 2026 09:39
@github-actions
Copy link
Copy Markdown

Seems you are using me but didn't get OPENAI_API_KEY seted in Variables/Secrets for this repo. you could follow readme for more information

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

0 participants