[renovate] Update dependency storybook to v10.1.10 [SECURITY] #588
Conversation
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
✅ Deploy Preview for echoes-react ready!
To edit notification comments on pull requests, go to your Netlify project configuration. |
|
Renovate Jira issue ID: ECHOES-1098 |
gregaubert
changed the title
gregaubert
force-pushed
the
renovate/npm-storybook-vulnerability
branch
from
d0739ba to
2dc08ad
Compare
Contributor
Author
Edited/Blocked NotificationRenovate will not automatically rebase this PR, because it does not recognize the last commit author and assumes somebody else may have edited the PR. You can manually request rebase by checking the rebase/retry box above. |
gregaubert
force-pushed
the
renovate/npm-storybook-vulnerability
branch
from
2dc08ad to
526cb99
Compare
|
gregaubert
added a commit
that referenced
this pull request
Jan 6, 2026
Co-authored-by: renovate[bot] <29139614+renovate[bot]@users.noreply.github.com> Co-authored-by: Grégoire Aubert <gregoire.aubert@sonarsource.com>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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:
9.0.18->9.1.17Storybook 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 OSV and the GitHub Advisory Database (CC-BY 4.0).
Release Notes
storybookjs/storybook (storybook)
v9.1.17Compare Source
v9.1.16Compare Source
v9.1.15Compare Source
preview-first-loadtelemetry - #32770, thanks @shilman!vite-plugin-storybook-nextjs- #32821, thanks @ndelangen!v9.1.14Compare Source
play-fntag for methods - #32695, thanks @shilman!v9.1.13Compare Source
v9.1.12Compare Source
v9.1.11Compare Source
sb.mockusage in Storybook's deployed in subpaths - #32678, thanks @valentinpalkovic!v9.1.10Compare Source
v9.1.9Compare Source
HTMLAttributesdocgen when using utility types - #32173, thanks @steciuk!v9.1.8Compare Source
nodeentry point - #32534, thanks @ndelangen!v9.1.7Compare Source
vite-plugin-storybook-nextjsto 2.0.7 - #32331, thanks @k35o!@ts-expect-errorin preview - #32442, thanks @mrginglymus!v9.1.6Compare Source
create-storybook- #32344, thanks @shilman!v9.1.5Compare Source
satisfies x as ysyntax - #32169, thanks @diagramatics!v9.1.4Compare Source
docgenoption to disable docgen processing - #32319, thanks @copilot-swe-agent!@sveltejs/vite-plugin-sveltev6 - #32320, thanks @JReinhold!v9.1.3Compare Source
v9.1.2Compare Source
entry.polyfillsundefined error - #32230, thanks @sk-pub!v9.1.1Compare Source
v9.1.0Compare 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.mockAPI 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
extendAPI, portable stories - #30601, thanks @kasperpeulen!react-element-to-jsx-string- #31170, thanks @7rulnik!project.jsonfor getAbsolutePath - #31510, thanks @ndelangen!Configuration
📅 Schedule: Branch creation - "" in timezone CET, 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.
This PR has been generated by Renovate Bot.
To know more about the whole process, check our WebApp dependencies management xtranet page.