Update dependency storybook to v8.6.15 [SECURITY]

[renovate]

This PR contains the following updates:

Package	Change	Age	Confidence
storybook (source)	8.6.14 → 8.6.15

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)

v8.6.15

Compare Source

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

---

Configuration

📅 Schedule: (in timezone Etc/UTC)

• Branch creation
  • ""
• Automerge
  • Only on Sunday and Saturday (* * * * 0,6)
  • Between 12:00 AM and 12:59 PM, only on Monday (* 0-12 * * 1)
  • Between 10:00 PM and 11:59 PM, Monday through Friday (* 22-23 * * 1-5)
  • Between 12:00 AM and 04:59 AM, Tuesday through Saturday (* 0-4 * * 2-6)

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

[codecov]

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 73.46%. Comparing base (4f95056) to head (6519a94).
⚠️ Report is 6 commits behind head on main.

Additional details and impacted files

@@            Coverage Diff             @@
##             main   #27172      +/-   ##
==========================================
- Coverage   73.46%   73.46%   -0.01%     
==========================================
  Files        1545     1545              
  Lines      123686   123686              
  Branches    14961    14961              
==========================================
- Hits        90870    90866       -4     
+ Misses      31819    31799      -20     
- Partials      997     1021      +24     

Flag	Coverage Δ
admin-tests	54.37% <ø> (-0.03%)	⬇️
e2e-tests	73.46% <ø> (-0.01%)	⬇️

Flags with carried forward coverage won't be shown. Click here to find out more.

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

🚀 New features to boost your workflow:

• ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.
• 📦 JS Bundle Analysis: Save yourself from yourself by tracking and limiting bundle sizes in JS merges.

[github-actions]

E2E Tests Failed

To view the Playwright test report locally, run:

REPORT_DIR=$(mktemp -d) && gh run download 24182732044 -n playwright-report -D "$REPORT_DIR" && npx playwright show-report "$REPORT_DIR"

[sonarqubecloud]

Quality Gate passed

Issues
0 New issues
0 Accepted issues

Measures
0 Security Hotspots
0.0% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarQube Cloud

[renovate]

Edited/Blocked Notification

Renovate 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.

⚠️ Warning: custom changes will be lost.