cve.bz

CVE-2025-68429 storybook storybook

5.3 mediumEPSS 0.3%Fix available

Medium (5.3) in storybook storybook. EPSS 0.3% estimated probability of exploitation activity in the next 30 days. Fixed in storybook 10.1.10, 7.6.21, 8.6.15.

On this page
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.

Severity

CVSS 3.1

5.3 medium
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N
EPSS
0.3% (unchanged from 0.3% a week ago; 0.3% 30 days ago) estimated probability of exploitation activity in the next 30 days; 20th percentile. Scored 2026-11-22. A forecast for this CVE across the internet, not for your own systems.
CISA's assessment (SSVC)
Exploitation: none · Automatable: yes · Technical impact: partial, assessed 2025-12-18. From CISA's Vulnrichment in the CVE List: whether it is exploited, whether exploiting it can be automated, and how much control it gives.
CWEs
CWE-200 Exposure of Sensitive Information to an Unauthorized Actor
CWE-538 Insertion of Sensitive Information into Externally-Accessible File or Directory
CWE-541 Inclusion of Sensitive Information in an Include File
OWASP Top 10
A01:2025 Broken Access Control
Published
Modified
NVD analysis
Analyzed
Record from
the NVD, synced

Fix and patched versions

Ask an AI about this CVE

Show the promptExplain CVE-2025-68429 for an engineer deciding whether to act. Use https://cve.bz/api/public/cves/CVE-2025-68429?via=ask-ai-copy and https://cve.bz/cve/CVE-2025-68429?via=ask-ai-copy as the source of truth: what is affected and which versions fix it, whether it is in CISA KEV, public exploits, and its EPSS (an internet-wide 30-day estimate of exploitation activity, not a forecast for my systems). If they give no fixed versions, use the CVE record https://cveawg.mitre.org/api/cve/CVE-2025-68429 or the vendor advisory, not third-party mirrors. Tell me how to check whether I am affected and how to verify a fix. Cite the sources and say where they are uncertain.

Opens a third-party assistant; its answer is its own, not cve.bz's. The prompt holds only this CVE's id and public links.

Affected

Versions

From the NVD's CPE matches.

ProductAffected
storybook:storybookfrom 7.0.0 before 7.6.21
storybook:storybookfrom 8.0.0 before 8.6.15
storybook:storybookfrom 9.0.0 before 9.1.17
storybook:storybookfrom 10.0.0 before 10.1.10

Packages (OSV)

AdvisoryEcosystemPackageAffectedFixed in
GHSA-8452-54wp-rmv6npmstorybook>=7.0.0 <7.6.217.6.21
GHSA-8452-54wp-rmv6npmstorybook>=8.0.0 <8.6.158.6.15
GHSA-8452-54wp-rmv6npmstorybook>=9.0.0 <9.1.179.1.17
GHSA-8452-54wp-rmv6npmstorybook>=10.0.0 <10.1.1010.1.10

Red Hat

Red Hat rates this Important.

Red Hat's statement

This vulnerability is rated Important for Red Hat as it can lead to the unintended exposure of sensitive environment variables. This occurs when a Storybook project is built using the `storybook build` command in a directory containing a `.env` file, and the resulting bundle is subsequently published to a web-accessible location. Storybook instances built without `.env` files or run in development mode (`storybook dev`) are not affected.

ProductPackageStateAdvisory
Multicluster Global Hub 1.4.9multicluster-globalhub/multicluster-globalhub-grafana-rhel9:1770126537Fixed 2026-02-11RHSA-2026:2500
Multicluster Global Hub 1.5.8multicluster-globalhub/multicluster-globalhub-grafana-rhel9:1770109405Fixed 2026-02-09RHSA-2026:2256
Red Hat Ceph Storage 8rhceph/grafana-rhel9:1770630607Fixed 2026-02-16RHSA-2026:2737
Node HealthCheck Operatorworkload-availability/node-healthcheck-must-gather-rhel9Not affected
Node HealthCheck Operatorworkload-availability/node-healthcheck-operator-bundleNot affected
Node HealthCheck Operatorworkload-availability/node-healthcheck-rhel9-operatorNot affected
Node HealthCheck Operatorworkload-availability/node-remediation-console-rhel9Not affected
Red Hat Advanced Cluster Management for Kubernetes 2rhacm2/acm-grafana-rhel9Affected
Red Hat Enterprise Linux 10grafanaNot affected
Red Hat Enterprise Linux 9grafanaNot affected
streams for Apache Kafka 2com.github.streamshub-consoleNot affected
streams for Apache Kafka 3com.github.streamshub-consoleWill not fix

Contains Red Hat Security Data © Red Hat, Inc., licensed under CC BY 4.0. Source: https://access.redhat.com/security/data. Modified: reformatted. Red Hat's page for CVE-2025-68429.

Attack patterns (CAPEC)

  • CAPEC-95 WSDL Scanning Likelihood: High · Severity: High

The attack patterns MITRE's CAPEC relates to this record's weaknesses, as MITRE names them. Credits. More on the page of CWE-200 (59).

References

Check your stackJSON