dbcve.org
StorybookApplication

CVE-2025-68429

MEDIUM · 5.3 CVSS v3.1 Published 2025-12-17
Fix available
A fix is available. Upgrade to 7.6.21 / 8.6.15 or later.
See remediation →
62/100
Remediation priority · Elevated
Remotely reachable No privileges Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
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.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

Storybook versions prior to 7.6.21/8.6.15/9.1.17/10.1.10 bundled environment variables from `.env` files into the JavaScript bundle during the `storybook build` process, making them visible in plaintext to anyone viewing the published Storybook's source code.

MitigationUpgrade Storybook to version 7.6.21, 8.6.15, 9.1.17, or 10.1.10 or higher, audit for any exposed secrets and rotate them, and use the `STORYBOOK_` prefix or Storybook's `env` config property for future variable handling.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
StorybookApplication
Affected:>= 7.0.0, < 7.6.21>= 8.0.0, < 8.6.15>= 9.0.0, < 9.1.17>= 10.0.0, < 10.1.10

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
None
User interaction
None
Scope
Unchanged
Confidentiality
Low
Integrity
None
Availability
None

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Check installed Storybook version
    Run `npm list @storybook/core` or check the `package.json` dependencies for the @storybook/core or storybook version number
    Affected if The installed version falls within one of these ranges: >= 7.0.0 and < 7.6.21, >= 8.0.0 and < 8.6.15, >= 9.0.0 and < 9.1.17, or >= 10.0.0 and < 10.1.10
  2. Verify .env files exist in the project
    Look for `.env`, `.env.local`, `.env.development`, `.env.production`, or similar files in the project root directory
    Affected if Sensitive environment variables were defined in .env files in the project directory
  3. Confirm Storybook was built and published
    Locate the built Storybook static files, typically in a `storybook-static` folder or similar output directory from running `storybook build`
    Affected if A Storybook build output exists and has been deployed or shared publicly
  4. Search built JavaScript for secret values
    Open the compiled JavaScript files in the storybook-static folder and search for plaintext strings that match values from your .env files (e.g., API keys, passwords, tokens)
    Affected if Any sensitive values from .env files appear as plaintext strings in the built JavaScript files

You are affected if you used an affected Storybook version, had sensitive variables in .env files, and built/deployed the Storybook with those secrets exposed in the JavaScript bundle.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Upgrade available Upgrade to 7.6.21 / 8.6.15 / 9.1.17 or later
Fixed in 7.6.218.6.159.1.17
Interim mitigation

Upgrade Storybook to version 7.6.21, 8.6.15, 9.1.17, or 10.1.10 or higher, audit for any exposed secrets and rotate them, and use the `STORYBOOK_` prefix or Storybook's `env` config property for future variable handling.

Recommended fix High confidence

7.6.21 (for 7.x) | 8.6.15 (for 8.x) | 9.1.17 (for 9.x) | 10.1.10 (for 10.x)

  1. Identify the current Storybook version in your project by checking package.json
  2. Upgrade Storybook to the appropriate fixed version based on your current major version: 7.x users upgrade to 7.6.21, 8.x users upgrade to 8.6.15, 9.x users upgrade to 9.1.17, or 10.x users upgrade to 10.1.10
  3. Run npm install or yarn to update dependencies
  4. Audit your .env files for any sensitive secrets that may have been exposed in previous builds
  5. Rotate any exposed API keys, tokens, or secrets identified in .env files
  6. If your project relies on reading environment variables after this update, either prefix them with STORYBOOK_ or configure them using the env property in .storybook/main.js
  7. Rebuild your Storybook with the updated version to verify the fix is applied
Caveat Projects relying on undocumented .env variable bundling behavior will need to use STORYBOOK_ prefix or configure env in .storybook/main.js to maintain access to environment variables after upgrade

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Storybook Scoped from the published advisory
  • Consultation2.0 h
  • Implementation2.0 h
  • Testing3.0 h
  • Review / QA1.0 h
8.0 hours of engineering $1,390
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,224.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2025-68429 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2025-68429 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data