CVE-2025-68429 Storybook manager bundle may expose environment variables during build
Attackers can view sensitive environment variables exposed in Storybook build artifacts if a .env file exists during the build process.
- Exploited in the wild
- Not known
- Login needed
- Not needed
- Attackable
- Over the internet
- Victim action needed
- Not needed
- Fix
- Available
What is CVE-2025-68429?
CVE-2025-68429 is a high-severity vulnerability in storybookjs storybook, published on 17 Dec 2025. An attacker can exploit it over the internet without logging in, with no action from the victim.
Official description
Storybook is a frontend workshop for building user interface components and pages in isolation. A vulnerability present starting in versions 7.0.0 and prior to versions 7.6.21, 8.6.15, 9.1.17, and 10.1.10 relates to Storybook’s handling of 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. For a project to potentially 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`) and 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. Storybook runtime environments (i.e. `storybook dev`) are not affected. Deployed applications that share a repo with your Storybook are not affected. Users should upgrade their Storybook—on both their local machines and CI environment—to version .6.21, 8.6.15, 9.1.17, or 10.1.10 as soon as possible. Maintainers additionally recommend that users audit for any sensitive secrets provided via `.env` files and rotate those keys. 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, 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.
Which versions are affected by CVE-2025-68429?
8 open source packages ship an affected version, including storybook. It affects 1 product.
| Package | Affected | Fixed in |
|---|---|---|
storybook npm | From 10.0.0 | 10.1.10 |
storybook npm | From 10.0.0 | 10.1.10 |
storybook npm | From 7.0.0 | 7.6.21 |
storybook npm | From 7.0.0 | 7.6.21 |
storybook npm | From 8.0.0 | 8.6.15 |
storybook npm | From 8.0.0 | 8.6.15 |
2 more packages
storybook npm | From 9.0.0 | 9.1.17 |
storybook npm | From 9.0.0 | 9.1.17 |
Products include Storybook Storybook.
How do I fix CVE-2025-68429?
Upgrade storybook to a fixed version for your release line: 10.1.10, 7.6.21, 8.6.15 or 9.1.17.
Is CVE-2025-68429 being exploited?
There is no known exploitation of CVE-2025-68429 in the wild and no public exploit code.
Other vulnerabilities in storybookjs storybook
Sources
Also known as CLSA-2026-1791983867, CLSA-2026-1792160913, CLSA-2026-1792161049, CLSA-2026-1792161051, CLSA-2026-1792161053, CLSA-2026-1792161057 and 70 more.