Update dependency storybook to v7.6.21 [SECURITY]

[renovate]

This PR contains the following updates:

Package	Change	Age	Confidence
storybook (source)	7.6.20 → 7.6.21

---

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

• https://github.com/storybookjs/storybook/security/advisories/GHSA-8452-54wp-rmv6
• https://nvd.nist.gov/vuln/detail/CVE-2025-68429
• https://storybook.js.org/blog/security-advisory
• https://github.com/advisories/GHSA-8452-54wp-rmv6

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

---

Release Notes

storybookjs/storybook (storybook)

v7.6.21

Compare Source

7.6.21

• Core: Fix .env-file parsing, thanks @​jreinhold!

---

Configuration

📅 Schedule: (UTC)

• Branch creation
  • At any time (no schedule defined)
• Automerge
  • "after 8pm and before 8am every weekday,every weekend"

🚦 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]

⚠️ Artifact update problem

Renovate failed to update an artifact related to this branch. You probably do not want to merge this PR as-is.

♻ Renovate will retry this branch, including artifacts, only when one of the following happens:

• any of the package files in this branch needs updating, or
• the branch becomes conflicted, or
• you click the rebase/retry checkbox if found above, or
• you rename this PR's title to start with "rebase!" to trigger it manually

The artifact failure details are included below:

File name: pnpm-lock.yaml

warn: This version of pnpm requires at least Node.js v22.13
warn: The current version of Node.js is v20.20.2
warn: Visit https://r.pnpm.io/comp to see the list of past pnpm versions with respective Node.js version support.
node:internal/modules/cjs/loader:1031
      throw new ERR_UNKNOWN_BUILTIN_MODULE(request);
            ^

Error [ERR_UNKNOWN_BUILTIN_MODULE]: No such built-in module: node:sqlite
    at Module._load (node:internal/modules/cjs/loader:1031:13)
    at Module.require (node:internal/modules/cjs/loader:1289:19)
    at require (node:internal/modules/helpers:182:18)
    at ../store/index/lib/index.js (file:///opt/containerbase/tools/pnpm/11.13.1/20.20.2/node_modules/pnpm/dist/pnpm.mjs:99639:25)
    at __init (file:///opt/containerbase/tools/pnpm/11.13.1/20.20.2/node_modules/pnpm/dist/pnpm.mjs:17:58)
    at ../resolving/npm-resolver/lib/index.js (file:///opt/containerbase/tools/pnpm/11.13.1/20.20.2/node_modules/pnpm/dist/pnpm.mjs:104731:5)
    at __init (file:///opt/containerbase/tools/pnpm/11.13.1/20.20.2/node_modules/pnpm/dist/pnpm.mjs:17:58)
    at ../workspace/projects-graph/lib/index.js (file:///opt/containerbase/tools/pnpm/11.13.1/20.20.2/node_modules/pnpm/dist/pnpm.mjs:104869:5)
    at __init (file:///opt/containerbase/tools/pnpm/11.13.1/20.20.2/node_modules/pnpm/dist/pnpm.mjs:17:58)
    at ../workspace/projects-filter/lib/index.js (file:///opt/containerbase/tools/pnpm/11.13.1/20.20.2/node_modules/pnpm/dist/pnpm.mjs:106269:5) {
  code: 'ERR_UNKNOWN_BUILTIN_MODULE'
}

Node.js v20.20.2