CVE-2025-68429: Storybook Storybook Manager Bundle May Expose Vulnerability
HIGHCVE-2025-68429 is a HIGH (CVSS 7.3) storybook manager bundle may expose vulnerability (CWE-538: Insertion of Sensitive Information into Externally-Accessible File or Directory) affecting Storybook libraries in the npm ecosystem. The issue involves storybook manager bundle may expose environment variables during build. Remediation is available by upgrading affected packages to version 8.6.15, 9.1.17, 10.1.10, 7.6.21.
CVE-2025-68429 at a Glance
Security Impact
CVSS: 7.3
The security impact metrics below are parsed directly from the CVSS v3.1 vector string (CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:L).
How to Fix CVE-2025-68429
To remediate this vulnerability, upgrade all affected Storybook dependencies to a patched release. Both direct and transitive dependencies should be checked, as frameworks or security libraries may pull in vulnerable versions transitively.
npm install storybook@8.6.15
npm install storybook@9.1.17
npm install storybook@10.1.10
npm install storybook@7.6.21
Run the following command in your project directory to verify that all resolved dependencies use the patched release:
npm ls storybook
How to Check if You Are Affected
To determine whether your Node.js application is affected by CVE-2025-68429, inspect your project dependencies using npm:
npm ls storybook
Analyze the terminal output to locate any version of Storybook in your dependency tree. If any resolved version matches the vulnerable ranges listed in the table below (for example, versions earlier than 8.6.15), your application is affected.
Note: The npm ls storybook command inspects dependencies declared in your package.json and lockfile; it does not perform automated runtime dynamic scanning.
Technical Details
Vulnerability Mechanism & Technical Analysis
This vulnerability is classified under CWE-538: Insertion of Sensitive Information into Externally-Accessible File or Directory, where the product places sensitive information into files or directories that are accessible to actors who are allowed to have access to the files, but not to the sensitive information. In Storybook, software state validation or input boundaries are circumvented during processing. Review the official source advisory statement below for specific affected components, classes, and reproduction details.
Source Advisory Statement
CVE-2025-68429 Affected Storybook Versions
4 component(s)| Product / Package | Ecosystem | Affected Versions | Fixed Version |
|---|---|---|---|
|
storybook
|
npm |
≥ 8.0.0
< 8.6.15
|
8.6.15
|
|
storybook
|
npm |
≥ 9.0.0
< 9.1.17
|
9.1.17
|
|
storybook
|
npm |
≥ 10.0.0
< 10.1.10
|
10.1.10
|
|
storybook
|
npm |
≥ 7.0.0
< 7.6.21
|
7.6.21
|
References
Frequently Asked Questions
What is CVE-2025-68429?
Which Storybook versions are affected?
What version fixes CVE-2025-68429?
Is storybook affected?
What is the CVSS score of CVE-2025-68429?
What CWE is associated with CVE-2025-68429?
How can I check npm dependencies for CVE-2025-68429?
Machine-readable OSV JSON
OSV v1.5 Schema
{
"schema_version" : "1.4.0",
"id" : "GHSA-8452-54wp-rmv6",
"modified" : "2025-12-18T18:49:21Z",
"published" : "2025-12-18T18:49:21Z",
"aliases" : [ "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. \n\nThe 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.\n\n## Who is impacted?\n\nFor a project to be vulnerable to this issue, it must:\n\n- Build the Storybook (i.e. run `storybook build` directly or indirectly) in a directory that contains a `.env` file (including variants like `.env.local`)\n- The `.env` file contains sensitive secrets\n- Use Storybook version `7.0.0` or above\n- Publish the built Storybook to the web\n\nStorybooks 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.\n\nUsers' Storybook runtime environments (i.e. `storybook dev`) are not affected. Deployed applications that share a repo with a project's Storybook are not affected.\n\nStorybook 6 and below are not affected.\n\n## Recommended actions\n\nFirst, Storybook recommends that everyone audit for any sensitive secrets provided via `.env` files and rotate those keys.\n\nSecond, 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**.\n\n- `10.1.10+`\n- `9.1.17+`\n- `8.6.15+`\n- `7.6.21+`\n\nFinally, 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](https://storybook.js.org/docs/configure/environment-variables#using-storybook-configuration) to manually specify values. In either case, **do not** include sensitive secrets as they *will* be included in the built bundle.\n\n## Further information\n\nDetails of the vulnerability can be found on the [Storybook announcement](https://storybook.js.org/blog/security-advisory).",
"severity" : [ {
"type" : "CVSS_V3",
"score" : "CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:L"
} ],
"affected" : [ {
"package" : {
"ecosystem" : "npm",
"name" : "storybook"
},
"ranges" : [ {
"type" : "ECOSYSTEM",
"events" : [ {
"introduced" : "7.0.0"
}, {
"fixed" : "7.6.21"
} ]
} ]
}, {
"package" : {
"ecosystem" : "npm",
"name" : "storybook"
},
"ranges" : [ {
"type" : "ECOSYSTEM",
"events" : [ {
"introduced" : "8.0.0"
}, {
"fixed" : "8.6.15"
} ]
} ]
}, {
"package" : {
"ecosystem" : "npm",
"name" : "storybook"
},
"ranges" : [ {
"type" : "ECOSYSTEM",
"events" : [ {
"introduced" : "9.0.0"
}, {
"fixed" : "9.1.17"
} ]
} ]
}, {
"package" : {
"ecosystem" : "npm",
"name" : "storybook"
},
"ranges" : [ {
"type" : "ECOSYSTEM",
"events" : [ {
"introduced" : "10.0.0"
}, {
"fixed" : "10.1.10"
} ]
} ]
} ],
"references" : [ {
"type" : "WEB",
"url" : "https://github.com/storybookjs/storybook/security/advisories/GHSA-8452-54wp-rmv6"
}, {
"type" : "ADVISORY",
"url" : "https://nvd.nist.gov/vuln/detail/CVE-2025-68429"
}, {
"type" : "PACKAGE",
"url" : "https://github.com/storybookjs/storybook"
}, {
"type" : "WEB",
"url" : "https://storybook.js.org/blog/security-advisory"
} ],
"database_specific" : {
"cwe_ids" : [ "CWE-200", "CWE-538", "CWE-541" ],
"severity" : "HIGH",
"github_reviewed" : true,
"github_reviewed_at" : "2025-12-18T18:49:21Z",
"nvd_published_at" : "2025-12-17T23:16:05Z"
}
}