CVE-2025-68429

HIGHNVD 7.37.3
EchelonGraph scoreMEDIUM confidence

“—” beside the score: it is equal to NVD's CVSS score.

This high-severity CVE scores 7.3 under NVD CVSS v3. EPSS exploit probability: 0.3% (16th percentile of EPSS-scored CVEs). No GitHub Security Advisory CVSS is on record for this CVE.

Triggered by: Headline CVSS from NVD CVSS v3
Sources: EPSS, NVD CVSS v3
7.3EG
EchelonGraph verdictPlan a fixRemediate within your standard update timelines at low or medium mission impact and sooner than that at high (the SSVC decision on this page).
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0.3%CVSS: 7.3Exploit: None knownExposed services: Not assessed

A fix is available — apply it.

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.

CVSS v3
7.3
EG Score
7.3HIGHmedium confidence
EG Risk
48
EG Risk 48/100

EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).

How it’s computed (value × EchelonGraph’s weight)
Severity73% × 45%
The EG Score, 7.3 of 10.
Exploitation0.3% × 40%
FIRST EPSS: the 30-day exploitation probability when EchelonGraph scored this CVE.
Automatability100% × 15%
CISA's SSVC Automatable value: yes (Vulnrichment).
SSVC (CISA's decision table, applied by EchelonGraph): Track at low or medium mission impact; Attend at high (mission-essential systems).
Exploitation none (CISA Vulnrichment) · Automatable yes (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE.
Action: A fix is available. Apply it within your standard update timelines at low or medium mission impact and sooner than that at high.
EPSS PROB
0.3%
EPSS %ILE
16th
KEV
Not listed

SSVC (CISA's decision table, applied by EchelonGraph)Track at low or medium mission impact; Attend at high (mission-essential systems).

A fix is available. Apply it within your standard update timelines at low or medium mission impact and sooner than that at high.

Exploitation none (CISA Vulnrichment) · Automatable yes (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE. Mission impact is CISA's Mission & Well-being decision point, and only you can judge it. CISA's table makes it high when Mission Prevalence is Essential — the vulnerable component "directly provides capabilities that constitute at least one MEF for at least one entity" (MEF: mission essential function) — or when Public Well-Being Impact is Irreversible: "multiple fatalities are likely", the cyber-physical system "is likely lost or destroyed", "extreme or serious externalities" are imposed on other parties, or social systems such as elections or the financial grid "are destabilized and potentially collapse". CISA's decision table

BOD 26-04 (CISA's remediation timeline, Table 1)14 days if the affected system is publicly exposed; 60 days if it is not.

In CISA KEV no (CISA's KEV catalog) · Automatable yes (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). Whether your system is publicly exposed is yours to answer. BOD 26-04 binds US Federal Civilian Executive Branch agencies; for anyone else it is CISA's published timeline, a reference rather than an obligation. The directive · how EchelonGraph applies it

Published

December 17, 2025

Last Modified

April 10, 2026

Advisory Details (2)

Auto-updated Aug 6, 2026
Patch available. Sources: github.
Web page

Security advisory

https://storybook.js.org/blog/security-advisory
GitHub advisoryMentions a patch (unverified)

Exposure of environment variables from .env in published Storybook · Advisory · storybookjs/storybook · GitHub

https://github.com/storybookjs/storybook/security/advisories/GHSA-8452-54wp-rmv6

Vendor Advisories for CVE-2025-68429(3)

These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.

Patch Availability(3)

Vendor / EcosystemFix (by version range) / PatchReleasedSource
redhatrhceph/grafana-rhel9:17706306072026-02-16redhat
redhatmulticluster-globalhub/multicluster-globalhub-grafana-rhel9:17701265372026-02-11redhat
redhatmulticluster-globalhub/multicluster-globalhub-grafana-rhel9:17701094052026-02-09redhat

Patches are aggregated from vendor advisories (Red Hat, Microsoft, Cisco, GitHub) and package ecosystems (OSV, GHSA). Multiple rows for the same upstream release have been deduplicated.

Affected Packages

(1 across 1 ecosystem)
npm(1)
PackageVulnerable rangeFix by version rangeDependents
storybook—
  • 7.0.0 up to 7.6.21: fixed in 7.6.21
  • 8.0.0 up to 8.6.15: fixed in 8.6.15
  • 9.0.0 up to 9.1.17: fixed in 9.1.17
  • 10.0.0 up to 10.1.10: fixed in 10.1.10
—

Weakness Classification(3)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Data Freshness Timeline

(refreshed 10× in last 7d / 29× in last 30d)

Each row is a time one of our pipelines fetched, updated or re-scored this CVE. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. An arrow marks a change the record states ("CVSS v3 → 9.1"); EPSS and GHSA rows show the values recorded at that time, not what changed (EPSS values are rounded; hover one for the exact figures). Most recent first.

Showing the most recent 90 of 185 refreshes on record for this CVE.

A repeat, a row identical to one the same pipeline wrote less than 10 seconds earlier, is not a separate refresh and is not counted. 10 repeat rows among the latest 100 are merged into the row they repeat. The 95 oldest rows on record are not shown and were not checked, so the counts can still include repeats.

  1. 2026-10-11 20:21 UTCEG score recompute
  2. 2026-10-11 18:34 UTCEG score recompute
  3. 2026-10-11 15:08 UTCEG score recompute
  4. 2026-10-11 13:47 UTCEPSS rescoreEPSS 0.3% · 16th percentile
  5. 2026-10-10 19:59 UTCEPSS rescoreEPSS 0.3% · 16th percentile
  6. 2026-10-09 20:06 UTCEPSS rescoreEPSS 0.3% · 16th percentile
  7. 2026-10-08 17:11 UTCEPSS rescoreEPSS 0.3% · 15th percentile
  8. 2026-10-07 23:47 UTCEPSS rescoreEPSS 0.3% · 15th percentile
  9. 2026-10-06 15:17 UTCEPSS rescoreEPSS 0.3% · 15th percentile
  10. 2026-10-05 17:42 UTCEPSS rescoreEPSS 0.3% · 15th percentile
  11. 2026-10-04 23:21 UTCEPSS rescoreEPSS 0.3% · 15th percentile
  12. 2026-10-03 16:19 UTCOSV refresh
  13. 2026-10-03 14:25 UTCEPSS rescoreEPSS 0.3% · 15th percentile
  14. 2026-10-01 19:49 UTCEPSS rescoreEPSS 0.3% · 15th percentile
  15. 2026-09-30 15:02 UTCEPSS rescoreEPSS 0.3% · 15th percentile
  16. 2026-09-29 15:20 UTCEPSS rescoreEPSS 0.3% · 15th percentile
  17. 2026-09-28 13:50 UTCEPSS rescoreEPSS 0.3% · 15th percentile
  18. 2026-09-26 15:58 UTCEPSS rescoreEPSS 0.3% · 15th percentile
  19. 2026-09-24 14:02 UTCEPSS rescoreEPSS 0.3% · 15th percentile
  20. 2026-09-23 13:47 UTCEPSS rescoreEPSS 0.3% · 17th percentile
  21. 2026-09-20 20:15 UTCEPSS rescoreEPSS 0.3% · 17th percentile
  22. 2026-09-18 19:27 UTCEPSS rescoreEPSS 0.3% · 17th percentile
  23. 2026-09-17 19:30 UTCEPSS rescoreEPSS 0.3% · 17th percentile
  24. 2026-09-16 14:07 UTCEPSS rescoreEPSS 0.3% · 17th percentile
  25. 2026-09-16 05:14 UTCEPSS rescoreEPSS 0.3% · 17th percentile
Show 65 more
  1. 2026-09-15 03:10 UTCEPSS rescoreEPSS 0.3% · 17th percentile
  2. 2026-09-14 07:20 UTCOSV refresh
  3. 2026-09-13 16:46 UTCEPSS rescoreEPSS 0.3% · 17th percentile
  4. 2026-09-12 15:00 UTCEPSS rescoreEPSS 0.3% · 17th percentile
  5. 2026-09-11 14:52 UTCEPSS rescoreEPSS 0.3% · 17th percentile
  6. 2026-09-11 09:36 UTCEPSS rescoreEPSS 0.3% · 17th percentile
  7. 2026-09-10 09:34 UTCEPSS rescoreEPSS 0.3% · 17th percentile
  8. 2026-09-08 22:00 UTCEPSS rescoreEPSS 0.3% · 17th percentile
  9. 2026-09-07 16:00 UTCEPSS rescoreEPSS 0.3% · 17th percentile
  10. 2026-09-06 13:47 UTCEPSS rescoreEPSS 0.3% · 17th percentile
  11. 2026-09-04 05:06 UTCEPSS rescoreEPSS 0.3% · 17th percentile
  12. 2026-09-02 14:11 UTCEPSS rescoreEPSS 0.3% · 17th percentile
  13. 2026-09-01 13:53 UTCEPSS rescoreEPSS 0.3% · 17th percentile
  14. 2026-08-30 01:21 UTCEPSS rescoreEPSS 0.3% · 17th percentile
  15. 2026-08-28 21:40 UTCEPSS rescoreEPSS 0.3% · 17th percentile
  16. 2026-08-26 14:45 UTCEPSS rescoreEPSS 0.3% · 17th percentile
  17. 2026-08-26 08:43 UTCOSV refresh
  18. 2026-08-25 13:48 UTCEPSS rescoreEPSS 0.3% · 17th percentile
  19. 2026-08-24 14:16 UTCEPSS rescoreEPSS 0.3% · 17th percentile
  20. 2026-08-23 00:18 UTCEPSS rescoreEPSS 0.3% · 18th percentile
  21. 2026-08-21 23:48 UTCEPSS rescoreEPSS 0.3% · 18th percentile
  22. 2026-08-20 22:55 UTCEPSS rescoreEPSS 0.3% · 18th percentile
  23. 2026-08-19 17:03 UTCEPSS rescoreEPSS 0.3% · 18th percentile
  24. 2026-08-18 13:48 UTCEPSS rescoreEPSS 0.3% · 18th percentile
  25. 2026-08-17 13:46 UTCEPSS rescoreEPSS 0.3% · 18th percentile
  26. 2026-08-16 14:55 UTCEPSS rescoreEPSS 0.3% · 18th percentile
  27. 2026-08-16 02:14 UTCEPSS rescoreEPSS 0.3% · 18th percentile
  28. 2026-08-15 01:30 UTCEPSS rescoreEPSS 0.3% · 17th percentile
  29. 2026-08-13 22:00 UTCEPSS rescoreEPSS 0.2% · 15th percentile
  30. 2026-08-12 13:50 UTCEPSS rescoreEPSS 0.2% · 15th percentile
  31. 2026-08-11 13:42 UTCEPSS rescoreEPSS 0.2% · 15th percentile
  32. 2026-08-10 23:59 UTCEPSS rescoreEPSS 0.2% · 15th percentile
  33. 2026-08-09 23:24 UTCEG score recompute
  34. 2026-08-09 23:24 UTCVendor advisory
  35. 2026-08-09 13:46 UTCEPSS rescoreEPSS 0.2% · 15th percentile
  36. 2026-08-08 16:36 UTCEPSS rescoreEPSS 0.2% · 15th percentile
  37. 2026-08-08 06:10 UTCEG score recompute
  38. 2026-08-08 06:10 UTCVendor advisory
  39. 2026-08-07 16:27 UTCEPSS rescoreEPSS 0.2% · 15th percentile
  40. 2026-08-06 07:53 UTCEG score recompute
  41. 2026-08-06 07:53 UTCVendor advisory
  42. 2026-08-05 19:17 UTCEPSS rescoreEPSS 0.2% · 15th percentile
  43. 2026-08-04 10:37 UTCEPSS rescoreEPSS 0.2% · 15th percentile
  44. 2026-08-03 10:35 UTCEPSS rescoreEPSS 0.2% · 15th percentile
  45. 2026-08-02 02:26 UTCEPSS rescoreEPSS 0.2% · 15th percentile
  46. 2026-08-01 04:15 UTCEPSS rescoreEPSS 0.2% · 15th percentile
  47. 2026-07-30 16:27 UTCEPSS rescoreEPSS 0.2% · 15th percentile
  48. 2026-07-30 01:30 UTCEPSS rescoreEPSS 0.2% · 15th percentile
  49. 2026-07-27 14:13 UTCEPSS rescoreEPSS 0.2% · 15th percentile
  50. 2026-07-27 04:39 UTCOSV refresh
  51. 2026-07-26 14:54 UTCEPSS rescoreEPSS 0.2% · 15th percentile
  52. 2026-07-25 14:17 UTCEPSS rescoreEPSS 0.2% · 15th percentile
  53. 2026-07-24 14:17 UTCEPSS rescoreEPSS 0.2% · 15th percentile
  54. 2026-07-23 14:18 UTCEPSS rescoreEPSS 0.2% · 15th percentile
  55. 2026-07-23 03:02 UTCEG score recompute
  56. 2026-07-22 14:08 UTCEPSS rescoreEPSS 0.2% · 15th percentile
  57. 2026-07-21 15:24 UTCEPSS rescoreEPSS 0.2% · 15th percentile
  58. 2026-07-20 17:08 UTCEPSS rescoreEPSS 0.2% · 15th percentile
  59. 2026-07-19 14:30 UTCEPSS rescoreEPSS 0.2% · 14th percentile
  60. 2026-07-19 02:28 UTCEPSS rescoreEPSS 0.2% · 14th percentile
  61. 2026-07-18 10:04 UTCEPSS rescoreEPSS 0.2% · 14th percentile
  62. 2026-07-16 17:02 UTCEPSS rescoreEPSS 0.2% · 14th percentile
  63. 2026-07-15 01:59 UTCEPSS rescoreEPSS 0.2% · 14th percentile
  64. 2026-07-13 06:12 UTCEPSS rescoreEPSS 0.2% · 14th percentile
  65. 2026-07-12 05:46 UTCEPSS rescoreEPSS 0.2% · 14th percentile

Related CVEs(same product + same vendor + same CWE)

Same product

1 shown

npm:storybook

Frequently asked(5)

What is CVE-2025-68429?
CVE-2025-68429 is a high-severity vulnerability; its CVE record was published on December 17, 2025. 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,…
When was the CVE record for CVE-2025-68429 published?
The CVE record for CVE-2025-68429 was published on December 17, 2025. That is the record's publication date; the vulnerability itself may have been made public earlier. EchelonGraph's copy of the record carries a last-modified date of April 10, 2026; the record at its source may have been updated since.
Is CVE-2025-68429 actively exploited?
CVE-2025-68429 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.3% probability of exploitation in the next 30 days (16th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2025-68429?
CVE-2025-68429 has a CVSS v3 base score of 7.3 (NVD).
How do I remediate CVE-2025-68429?
A fix for CVE-2025-68429 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2025-68429 are linked in the Vendor Advisories panel on this page.

Dependency Blast Radius

See which npm, PyPI, Go, and Maven packages are affected by CVE-2025-68429

Explore →

Is Your Infrastructure Affected by CVE-2025-68429?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.

Book a Demo →Browse All CVEs