Skip to content
Fencer Vulns
high 7.3

CVE-2025-68429 json

Storybook manager bundle may expose environment variables during build

published 2025-12-17 10 mo ago modified 2026-09-10 1 mo ago also EUVD-2025-204013 , GHSA-8452-54wp-rmv6

cvss
7.3
version 3.1, CNA
cisa kev
Not listed
not in CISA's catalog
epss
0.3%
EPSS 0.3% chance of exploitation in 30 days, percentile 17%
public exploits
0
none known

Summary

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.

Patch / fix

  • npm storybook 7.6.21, 8.6.15, 9.1.17, 10.1.10
  • storybook storybook 7.6.21, 8.6.15, 9.1.17, 10.1.10

Vendor advisories

What the vendors themselves say about their products: affected, fixed or not affected, and what to do.

red hat product security vex CVE-2025-68429 updated cvss 7.5

Storybook: Storybook: Information disclosure via unexpected bundling of environment variables

  • Red Hat Advanced Cluster Management for Kubernetes 2 rhacm2/acm-grafana-rhel9
    affected: no fix available
  • Red Hat streams for Apache Kafka 3 com.github.streamshub-console
    affected: no fix planned “Will not fix”
  • Red Hat Multicluster Global Hub 1.4.9 multicluster-globalhub 1770126537
    fixed: vendor fix RHSA-2026:2500
  • Red Hat Multicluster Global Hub 1.5.8 multicluster-globalhub 1770109405
    fixed: vendor fix RHSA-2026:2256
  • Red Hat Ceph Storage 8 rhceph 1770630607
    fixed: vendor fix RHSA-2026:2737
  • Red Hat Multicluster Global Hub 1.4.9 multicluster-globalhub 1769643304, multicluster-globalhub 1770280963, multicluster-globalhub 1770281189, multicluster-globalhub 1770281560, multicluster-globalhub 1770362687 Red Hat Multicluster Global Hub 1.5.8 multicluster-globalhub 1769643671, multicluster-globalhub 1770112094, multicluster-globalhub 1770112233, multicluster-globalhub 1770113032, multicluster-globalhub 1770124784 Red Hat Node HealthCheck Operator workload-availability/node-remediation-console-rhel9, workload-availability/node-healthcheck-rhel9-operator, workload-availability/node-healthcheck-operator-bundle, workload-availability/node-healthcheck-must-gather-rhel9 Red Hat Ceph Storage 8 rhceph 1770630907, rhceph 1770631713, rhceph 1770631941, rhceph 1770632172, rhceph 1770632233
    not affected: vulnerable code not present
  • Red Hat Enterprise Linux 9 grafana, grafana-selinux Red Hat Enterprise Linux 10 grafana Red Hat streams for Apache Kafka 2 com.github.streamshub-console
    not affected: vulnerable code not in execute path

Red Hat CSAF VEX © Red Hat, Inc., from https://security.access.redhat.com/data/csaf/v2/vex/; changed: reduced to product statuses and remediations. CC BY 4.0 · csaf

CISA SSVC

Exploitation
none
Automatable
yes
Technical impact
partial
Assessed
10 mo ago

Exploit prediction

0.26% chance of exploitation in the next 30 days, higher than 17% of all scored CVEs (FIRST EPSS, 2026-11-08).

CVSS scores

assigned by version score vector
CNA 3.1 7.3 CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:L
GitHub 3.1 7.3 CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:L
NVD 3.1 5.3 CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N

Affected packages

ecosystem package affected fixed in
npm storybook
>=7.0.0, <7.6.21
>=8.0.0, <8.6.15
>=9.0.0, <9.1.17
>=10.0.0, <10.1.10
7.6.21
8.6.15
9.1.17
10.1.10

Affected products

  • storybookjs storybook

Classification

Weakness
  • 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

References

Sources

Fencer Vulns keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.

CPEs and fixed versions use Anchore's correction of NVD's data: Added CPE configurations because not yet analyzed by NVD.