Advisory

GHSA-8452-54wp-rmv6

Also known as: CVE-2025-68429

Summary

Storybook manager bundle may expose environment variables during build

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

High Basis: The source's own band: HIGH

Dates

Published
2025-12-18 18:49 UTC
Modified
2026-09-10 03:50 UTC

Affected packages and fixes

storybook

npm · All systems

Affected

  • introduced 7.0.0, fixed 7.6.21 (semver)

Fixed versions

7.6.21

Fix

storybook

npm · All systems

Affected

  • introduced 8.0.0, fixed 8.6.15 (semver)

Fixed versions

8.6.15

Fix

storybook

npm · All systems

Affected

  • introduced 9.0.0, fixed 9.1.17 (semver)

Fixed versions

9.1.17

Fix

storybook

npm · All systems

Affected

  • introduced 10.0.0, fixed 10.1.10 (semver)

Fixed versions

10.1.10

Fix

Fix commands are the export's own generic commands. Ojuju never runs them. Check them against your setup first.

Check your own computer: guard packages check

View this record on OSV.dev

Source

Source: GitHub Advisory Database (reviewed advisories) · CC BY 4.0

Sources & licences