CVE-2026-27148

CRITICALNVD 9.69.6
EchelonGraph scoreMEDIUM confidence

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

This critical-severity CVE scores 9.6 under NVD CVSS v3. EPSS exploit probability: 0.6% (50th 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

Also known asEUVD-2026-8750 (ENISA EUVD) · GHSA-mjf5-7g4m-gx5w (GitHub Security Advisories)Source: ENISA EUVD

9.6EG
EchelonGraph verdictPlan a fixRemediate within your standard update timelines (the SSVC decision on this page).
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0.6%CVSS: 9.6Exploit: 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. Prior to versions 7.6.23, 8.6.17, 9.1.19, and 10.2.10, the WebSocket functionality in Storybook's dev server, used to create and update stories, is vulnerable to WebSocket hijacking. This vulnerability only affects the Storybook dev server; production builds are not impacted. Exploitation requires a developer to visit a malicious website while their local Storybook dev server is running. Because the WebSocket connection does not validate the origin of incoming connections, a malicious site can silently send WebSocket messages to the local instance without any further user interaction. If the Storybook dev server is intentionally exposed publicly (e.g. for design reviews or stakeholder demos) the risk is higher, as no malicious site visit is required. Any unauthenticated attacker can send WebSocket messages to it directly. The vulnerability affects the WebSocket message handlers for creating and saving stories. Both are vulnerable to injection via unsanitized input in the componentFilePath field, which can be exploited to achieve persistent XSS or Remote Code Execution (RCE). Versions 7.6.23, 8.6.17, 9.1.19, and 10.2.10 contain a fix for the issue.

CVSS v3
9.6
EG Score
9.6CRITICALmedium confidence
EG Risk
43
EG Risk 43/100

EG Risk is EchelonGraph's 0–100 priority score. It fuses impact severity (EG Severity, the CVSS base score, never the KEV-floored or EPSS-lifted EG Score) with real-world exploitation and automatability, under weights EchelonGraph set by hand, so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner.

How it’s computed (value × EchelonGraph’s weight)
Severity96% × 45%
Impact severity (EG Severity): CVSS 9.6 of 10. Never the KEV-floored or EPSS-lifted EG Score.
Exploitation0.6% × 40%
FIRST EPSS: the 30-day exploitation probability when EchelonGraph scored this CVE.
Automatability0% × 15%
CISA's SSVC Automatable value: no (Vulnrichment).
SSVC (CISA's decision table, applied by EchelonGraph): Track at low or medium mission impact; Track* at high (mission-essential systems).
Exploitation none (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact total (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.
EPSS PROB
0.6%
EPSS %ILE
50th
KEV
Not listed

What the EG score is made of (scorer v4.0: the three questions the 0–10 score mixes, published apart · methodology)

The EG score (9.6): severity, escalated by confirmed exploitation. This CVE's 9.6 is its impact severity (EG Severity), not escalated.

EG Severity
9.6 CRITICALCVSS-B, impact only: no KEV listing, EPSS or EG-KEV tier raises it.NVD CVSS v3 · CVSS v3.0 or v3.1
EG Likelihood
0.6% within 30 daysSource: FIRST EPSS (model v2026.06.15, score date 2026-11-12). FIRST's exploitation probability, not an EchelonGraph model.
Confirmed exploitation
None on record (CISA KEV, EG-KEV Tier 1)Reported apart from the likelihood: an observed fact, not a probability.
EG Priority
SSVC Track at medium mission impactTrack at low or medium mission impact; Track* at high (mission-essential systems).CISA BOD 26-04: 14 days if the affected system is publicly exposed; Fix on system upgrade if it is not.Each input and its source, and whom BOD 26-04 binds: the SSVC and BOD 26-04 blocks below.

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

A fix is available. Apply it within your standard update timelines.

Exploitation none (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact total (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; Fix on system upgrade if it is not.

The score's inputs: In CISA KEV no (CISA's KEV catalog) · Automatable no (CISA Vulnrichment) · Technical impact total (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

February 25, 2026

Last Modified

July 15, 2026

Advisory Details (10)

Auto-updated Oct 7, 2026
Patch available. Sources: github, redhat, github_commit, github_release.
Red HatMentions a patch (unverified)

CVE-2026-27148 - Red Hat Customer Portal

Affected: Red Hat Enterprise Linux 8 or OpenShift Container Platform 4, is affected by this vulnerability and a fix may be released to a

https://access.redhat.com/security/cve/CVE-2026-27148
GitHub advisoryMentions a patch (unverified)

Storybook dev server vulnerable to WebSocket hijacking · Advisory · storybookjs/storybook · GitHub

https://github.com/storybookjs/storybook/security/advisories/GHSA-mjf5-7g4m-gx5w
GitHub release Patch Available

v9.1.19

Patch available: storybookjs/storybook v9.1.19

https://github.com/storybookjs/storybook/releases/tag/v9.1.19
GitHub release Patch Available

v8.6.17

Patch available: storybookjs/storybook v8.6.17

https://github.com/storybookjs/storybook/releases/tag/v8.6.17
GitHub release Patch Available

v7.6.23

Patch available: storybookjs/storybook v7.6.23

https://github.com/storybookjs/storybook/releases/tag/v7.6.23
GitHub release Patch Available

v10.2.10

Patch available: storybookjs/storybook v10.2.10

https://github.com/storybookjs/storybook/releases/tag/v10.2.10
GitHub commit

commit d34085f39c64 (storybookjs/storybook)

Fix landed in storybookjs/storybook commit d34085f39c64 — awaiting tagged release

https://github.com/storybookjs/storybook/commit/d34085f39c647f5c23c3a3b2d197c18602fcf876
GitHub commit

commit b8cfa77c7394 (storybookjs/storybook)

Fix landed in storybookjs/storybook commit b8cfa77c7394 — awaiting tagged release

https://github.com/storybookjs/storybook/commit/b8cfa77c73940c140acdcd8a06ab1ea913c44761
GitHub commit

commit 54689a8add18 (storybookjs/storybook)

Fix landed in storybookjs/storybook commit 54689a8add18 — awaiting tagged release

https://github.com/storybookjs/storybook/commit/54689a8add18ea75d628c540f4bc677592a1e685
GitHub commit

commit 0affdf928bd6 (storybookjs/storybook)

Fix landed in storybookjs/storybook commit 0affdf928bd6 — awaiting tagged release

https://github.com/storybookjs/storybook/commit/0affdf928bd6fafbadfb1dfe22ce6104805e10e8

Vendor Advisories for CVE-2026-27148(1)

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
npmstorybook @ 8.6.17 (fixes >= 8.1.0, < 8.6.17)—ghsa
npmstorybook @ 9.1.19 (fixes >= 8.7.0-alpha.0, < 9.1.19)—ghsa
npmstorybook @ 10.2.10 (fixes >= 10.0.0-beta.0, < 10.2.10)—ghsa

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—
  • 8.1.0 up to 8.6.17: fixed in 8.6.17
  • 8.7.0-alpha.0 up to 9.1.19: fixed in 9.1.19
  • 10.0.0-beta.0 up to 10.2.10: fixed in 10.2.10
—

Weakness Classification(4)

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

Data Freshness Timeline

(refreshed 14× in last 7d / 44× 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 its CVE.org record (CNA or CISA ADP). 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). "EchelonGraph re-scored" is our own recompute of this CVE's score, not an update from a source, and is not counted in the refreshes above. Most recent first.

Showing the most recent 100 of 208 rows on record for this CVE, as 99 entries (1 repeat merged).

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. 1 repeat row among the latest 100 is merged into the row it repeats. The 108 oldest rows on record are not shown and were not checked, so the counts can still include repeats.

  1. 2026-11-13 16:51 UTCEPSS rescoreEPSS 0.6% · 50th percentile
  2. 2026-11-13 04:31 UTCEchelonGraph re-scored
  3. 2026-11-13 04:31 UTCGHSA enrichmentGHSA-mjf5-7g4m-gx5w · GitHub severity HIGH
  4. 2026-11-12 16:33 UTCEPSS rescoreEPSS 0.6% · 50th percentile
  5. 2026-11-12 03:50 UTCEchelonGraph re-scored
  6. 2026-11-12 03:50 UTCGHSA enrichmentGHSA-mjf5-7g4m-gx5w · GitHub severity HIGH
  7. 2026-11-11 16:39 UTCEPSS rescoreEPSS 0.6% · 50th percentile
  8. 2026-11-11 03:10 UTCEchelonGraph re-scored
  9. 2026-11-11 03:10 UTCGHSA enrichmentGHSA-mjf5-7g4m-gx5w · GitHub severity HIGH
  10. 2026-11-10 16:43 UTCEPSS rescoreEPSS 0.6% · 50th percentile
  11. 2026-11-10 02:29 UTCEchelonGraph re-scored
  12. 2026-11-10 02:29 UTCGHSA enrichmentGHSA-mjf5-7g4m-gx5w · GitHub severity HIGH
  13. 2026-11-09 16:34 UTCEPSS rescoreEPSS 0.6% · 50th percentile
  14. 2026-11-09 01:49 UTCEchelonGraph re-scored
  15. 2026-11-09 01:49 UTCGHSA enrichmentGHSA-mjf5-7g4m-gx5w · GitHub severity HIGH
  16. 2026-11-08 16:38 UTCEPSS rescoreEPSS 0.6% · 50th percentile
  17. 2026-11-08 01:09 UTCEchelonGraph re-scored
  18. 2026-11-08 01:09 UTCGHSA enrichmentGHSA-mjf5-7g4m-gx5w · GitHub severity HIGH
  19. 2026-11-07 16:38 UTCEPSS rescoreEPSS 0.6% · 50th percentile
  20. 2026-11-07 00:25 UTCEchelonGraph re-scored
  21. 2026-11-07 00:25 UTCGHSA enrichmentGHSA-mjf5-7g4m-gx5w · GitHub severity HIGH
  22. 2026-11-06 16:37 UTCEPSS rescoreEPSS 0.6% · 50th percentile
  23. 2026-11-06 04:25 UTCOSV refresh
  24. 2026-11-05 23:45 UTCEchelonGraph re-scored
  25. 2026-11-05 23:45 UTCGHSA enrichmentGHSA-mjf5-7g4m-gx5w · GitHub severity HIGH
Show 74 more
  1. 2026-11-05 16:37 UTCEPSS rescoreEPSS 0.6% · 50th percentile
  2. 2026-11-04 23:05 UTCEchelonGraph re-scored
  3. 2026-11-04 23:05 UTCGHSA enrichmentGHSA-mjf5-7g4m-gx5w · GitHub severity HIGH
  4. 2026-11-04 16:35 UTCEPSS rescoreEPSS 0.6% · 50th percentile
  5. 2026-11-03 22:24 UTCEchelonGraph re-scored
  6. 2026-11-03 22:24 UTCGHSA enrichmentGHSA-mjf5-7g4m-gx5w · GitHub severity HIGH
  7. 2026-11-03 16:47 UTCEPSS rescoreEPSS 0.6% · 50th percentile
  8. 2026-11-02 21:43 UTCEchelonGraph re-scored
  9. 2026-11-02 21:43 UTCGHSA enrichmentGHSA-mjf5-7g4m-gx5w · GitHub severity HIGH
  10. 2026-11-02 16:44 UTCEPSS rescoreEPSS 0.6% · 50th percentile
  11. 2026-11-01 21:03 UTCEchelonGraph re-scored
  12. 2026-11-01 21:03 UTCGHSA enrichmentGHSA-mjf5-7g4m-gx5w · GitHub severity HIGH
  13. 2026-11-01 16:34 UTCEPSS rescoreEPSS 0.6% · 50th percentile
  14. 2026-11-01 07:56 UTCGHSA enrichmentGHSA-mjf5-7g4m-gx5w · GitHub severity HIGH
  15. 2026-10-31 20:22 UTCEchelonGraph re-scored
  16. 2026-10-31 16:32 UTCEPSS rescoreEPSS 0.6% · 50th percentile
  17. 2026-10-30 19:43 UTCEchelonGraph re-scored
  18. 2026-10-30 16:34 UTCEPSS rescoreEPSS 0.6% · 50th percentile
  19. 2026-10-29 19:02 UTCEchelonGraph re-scored
  20. 2026-10-29 16:33 UTCEPSS rescoreEPSS 0.6% · 50th percentile
  21. 2026-10-28 18:22 UTCEchelonGraph re-scored
  22. 2026-10-28 16:32 UTCEPSS rescoreEPSS 0.6% · 50th percentile
  23. 2026-10-27 17:37 UTCEchelonGraph re-scored
  24. 2026-10-27 16:31 UTCEPSS rescoreEPSS 0.6% · 50th percentile
  25. 2026-10-26 16:57 UTCEchelonGraph re-scored
  26. 2026-10-26 16:31 UTCEPSS rescoreEPSS 0.6% · 49th percentile
  27. 2026-10-25 16:32 UTCEPSS rescoreEPSS 0.6% · 49th percentile
  28. 2026-10-25 14:39 UTCEchelonGraph re-scored
  29. 2026-10-24 16:32 UTCEPSS rescoreEPSS 0.7% · 52nd percentile
  30. 2026-10-24 15:19 UTCEchelonGraph re-scored
  31. 2026-10-23 16:31 UTCEPSS rescoreEPSS 0.7% · 52nd percentile
  32. 2026-10-23 14:39 UTCEchelonGraph re-scored
  33. 2026-10-22 16:34 UTCEPSS rescoreEPSS 0.6% · 49th percentile
  34. 2026-10-22 13:59 UTCEchelonGraph re-scored
  35. 2026-10-21 16:32 UTCEPSS rescoreEPSS 0.6% · 48th percentile
  36. 2026-10-21 13:18 UTCEchelonGraph re-scored
  37. 2026-10-20 16:32 UTCEPSS rescoreEPSS 0.6% · 48th percentile
  38. 2026-10-20 12:32 UTCEchelonGraph re-scored
  39. 2026-10-19 16:31 UTCEPSS rescoreEPSS 0.6% · 48th percentile
  40. 2026-10-19 11:49 UTCEchelonGraph re-scored
  41. 2026-10-18 16:31 UTCEPSS rescoreEPSS 0.6% · 48th percentile
  42. 2026-10-18 03:51 UTCEchelonGraph re-scored
  43. 2026-10-17 16:33 UTCEPSS rescoreEPSS 0.6% · 48th percentile
  44. 2026-10-17 08:28 UTCEchelonGraph re-scored
  45. 2026-10-16 16:41 UTCEPSS rescoreEPSS 0.6% · 48th percentile
  46. 2026-10-16 07:47 UTCEchelonGraph re-scored
  47. 2026-10-15 16:31 UTCEPSS rescoreEPSS 0.6% · 48th percentile
  48. 2026-10-15 06:47 UTCEchelonGraph re-scored
  49. 2026-10-14 16:32 UTCEPSS rescoreEPSS 0.6% · 48th percentile
  50. 2026-10-14 02:31 UTCEchelonGraph re-scored
  51. 2026-10-13 16:33 UTCEPSS rescoreEPSS 0.6% · 47th percentile
  52. 2026-10-12 22:45 UTCEchelonGraph re-scored
  53. 2026-10-12 16:33 UTCEPSS rescoreEPSS 0.6% · 47th percentile
  54. 2026-10-12 16:17 UTCEchelonGraph re-scored
  55. 2026-10-11 20:00 UTCEchelonGraph re-scored
  56. 2026-10-11 17:13 UTCEchelonGraph re-scored
  57. 2026-10-11 14:44 UTCEchelonGraph re-scored
  58. 2026-10-11 13:48 UTCEPSS rescoreEPSS 0.6% · 47th percentile
  59. 2026-10-10 20:00 UTCEPSS rescoreEPSS 0.6% · 47th percentile
  60. 2026-10-09 20:07 UTCEPSS rescoreEPSS 0.6% · 47th percentile
  61. 2026-10-09 13:58 UTCOSV refresh
  62. 2026-10-08 17:11 UTCEPSS rescoreEPSS 0.6% · 47th percentile
  63. 2026-10-07 23:47 UTCEPSS rescoreEPSS 0.6% · 47th percentile
  64. 2026-10-06 15:17 UTCEPSS rescoreEPSS 0.6% · 47th percentile
  65. 2026-10-05 17:42 UTCEPSS rescoreEPSS 0.6% · 47th percentile
  66. 2026-10-04 23:21 UTCEPSS rescoreEPSS 0.6% · 47th percentile
  67. 2026-10-03 14:25 UTCEPSS rescoreEPSS 0.6% · 47th percentile
  68. 2026-10-01 19:49 UTCEPSS rescoreEPSS 0.6% · 47th percentile
  69. 2026-09-30 15:03 UTCEPSS rescoreEPSS 0.6% · 47th percentile
  70. 2026-09-28 13:51 UTCEPSS rescoreEPSS 0.6% · 46th percentile
  71. 2026-09-26 15:58 UTCEPSS rescoreEPSS 0.6% · 46th percentile
  72. 2026-09-26 00:26 UTCEPSS rescoreEPSS 0.6% · 46th percentile
  73. 2026-09-20 20:15 UTCEPSS rescoreEPSS 0.5% · 44th percentile
  74. 2026-09-19 21:30 UTCOSV refresh

Frequently asked(5)

What is CVE-2026-27148?
CVE-2026-27148 is a critical-severity vulnerability; its CVE record was published on February 25, 2026. Storybook is a frontend workshop for building user interface components and pages in isolation. Prior to versions 7.6.23, 8.6.17, 9.1.19, and 10.2.10, the WebSocket functionality in Storybook's dev server, used to create and update stories, is vulnerable to WebSocket hijacking. This vulnerability…
When was the CVE record for CVE-2026-27148 published?
The CVE record for CVE-2026-27148 was published on February 25, 2026. 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 July 15, 2026; the record at its source may have been updated since.
Is CVE-2026-27148 actively exploited?
CVE-2026-27148 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.6% probability of exploitation in the next 30 days (50th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-27148?
CVE-2026-27148 has a CVSS v3 base score of 9.6 (NVD).
How do I remediate CVE-2026-27148?
A fix for CVE-2026-27148 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2026-27148 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-2026-27148

Explore →

Is Your Infrastructure Affected by CVE-2026-27148?

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