chore(deps): update dependency storybook to v7.6.21 [security] - #93
Open
renovate[bot] wants to merge 1 commit into
Open
chore(deps): update dependency storybook to v7.6.21 [security]#93renovate[bot] wants to merge 1 commit into
renovate[bot] wants to merge 1 commit into
Conversation
✅ Deploy Preview for timjames ready!
To edit notification comments on pull requests, go to your Netlify project configuration. |
renovate
Bot
force-pushed
the
renovate/npm-storybook-vulnerability
branch
2 times, most recently
from
January 7, 2026 02:20
7035c72 to
7fe42e7
Compare
renovate
Bot
force-pushed
the
renovate/npm-storybook-vulnerability
branch
from
January 8, 2026 19:16
7fe42e7 to
023c160
Compare
renovate
Bot
force-pushed
the
renovate/npm-storybook-vulnerability
branch
2 times, most recently
from
January 23, 2026 19:58
5023f0d to
dbbc1b4
Compare
renovate
Bot
force-pushed
the
renovate/npm-storybook-vulnerability
branch
from
February 2, 2026 21:02
dbbc1b4 to
a8a3262
Compare
renovate
Bot
force-pushed
the
renovate/npm-storybook-vulnerability
branch
2 times, most recently
from
February 17, 2026 15:34
1a34489 to
cb551e5
Compare
renovate
Bot
force-pushed
the
renovate/npm-storybook-vulnerability
branch
from
March 5, 2026 17:06
cb551e5 to
279c3ed
Compare
renovate
Bot
force-pushed
the
renovate/npm-storybook-vulnerability
branch
from
March 13, 2026 18:06
279c3ed to
d39a656
Compare
renovate
Bot
force-pushed
the
renovate/npm-storybook-vulnerability
branch
from
March 26, 2026 10:55
d39a656 to
1933353
Compare
auto-merge was automatically disabled
March 27, 2026 01:00
Pull request was closed
renovate
Bot
force-pushed
the
renovate/npm-storybook-vulnerability
branch
3 times, most recently
from
April 1, 2026 19:43
3de7e46 to
6ce8344
Compare
renovate
Bot
force-pushed
the
renovate/npm-storybook-vulnerability
branch
from
April 8, 2026 17:55
6ce8344 to
4bf34d4
Compare
renovate
Bot
force-pushed
the
renovate/npm-storybook-vulnerability
branch
from
April 29, 2026 14:13
4bf34d4 to
34dec92
Compare
renovate
Bot
force-pushed
the
renovate/npm-storybook-vulnerability
branch
2 times, most recently
from
May 18, 2026 09:32
d9cddb0 to
546210b
Compare
auto-merge was automatically disabled
May 23, 2026 16:28
Pull request was closed
renovate
Bot
force-pushed
the
renovate/npm-storybook-vulnerability
branch
2 times, most recently
from
May 23, 2026 21:08
546210b to
52056d4
Compare
renovate
Bot
force-pushed
the
renovate/npm-storybook-vulnerability
branch
3 times, most recently
from
June 3, 2026 15:15
22cbb94 to
e37e8dc
Compare
renovate
Bot
force-pushed
the
renovate/npm-storybook-vulnerability
branch
from
June 11, 2026 17:41
e37e8dc to
24a23f7
Compare
renovate
Bot
force-pushed
the
renovate/npm-storybook-vulnerability
branch
2 times, most recently
from
July 17, 2026 01:29
e85df5f to
86980c5
Compare
renovate
Bot
force-pushed
the
renovate/npm-storybook-vulnerability
branch
2 times, most recently
from
July 24, 2026 17:35
abfae04 to
5f2224d
Compare
renovate
Bot
force-pushed
the
renovate/npm-storybook-vulnerability
branch
from
July 30, 2026 15:14
5f2224d to
37f3d57
Compare
renovate
Bot
force-pushed
the
renovate/npm-storybook-vulnerability
branch
2 times, most recently
from
August 14, 2026 22:59
1a50de6 to
d1aa762
Compare
renovate
Bot
force-pushed
the
renovate/npm-storybook-vulnerability
branch
from
August 26, 2026 13:02
d1aa762 to
162553b
Compare
renovate
Bot
force-pushed
the
renovate/npm-storybook-vulnerability
branch
3 times, most recently
from
September 7, 2026 20:46
c54dd30 to
bf45d76
Compare
renovate
Bot
force-pushed
the
renovate/npm-storybook-vulnerability
branch
from
September 9, 2026 20:58
bf45d76 to
7264374
Compare
renovate
Bot
force-pushed
the
renovate/npm-storybook-vulnerability
branch
from
September 10, 2026 16:01
7264374 to
d548652
Compare
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
This PR contains the following updates:
7.6.16→7.6.21Storybook 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
.envfile, which could, in specific circumstances, lead to those variables being unexpectedly bundled into the artifacts created by thestorybook buildcommand. 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:
storybook builddirectly or indirectly) in a directory that contains a.envfile (including variants like.env.local).envfile contains sensitive secrets7.0.0or aboveStorybooks built without a
.envfile at build time are not affected, including common CI-based builds where secrets are provided via platform environment variables rather than.envfiles.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
.envfiles 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 theenvproperty 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:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:LReferences
This data is provided by the GitHub Advisory Database (CC-BY 4.0).
Release Notes
storybookjs/storybook (storybook)
v7.6.21Compare Source
7.6.21
v7.6.20Compare Source
v7.6.19Compare Source
7.6.19
7.6.18containing wrong dependency identifiers, thanks @jreinhold!v7.6.18Compare Source
7.6.18
v7.6.17Compare Source
Configuration
📅 Schedule: (in timezone Australia/Sydney)
🚦 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.
This PR was generated by Mend Renovate. View the repository job log.