Home › Vulnerabilities

Storybook Flaw CVE-2026-114125: Update Now

Published October 31, 2026 · Last updated October 31, 2026

CVE Patch

The short version: CVE-2026-114125 is a high-severity security flaw in Storybook. The National Vulnerability Database (NVD) published it on October 21, 2026, and the score it lists is 8.6 out of 10. When FraudMeNot checked on October 31, 2026, CISA had not added CVE-2026-114125 to its Known Exploited Vulnerabilities catalog, so there was no public U.S. government confirmation of attacks yet. A fix is available, which is why this page focuses on who should update and how.

What the official record says about CVE-2026-114125

The record was filed by github.com. In its own words: "Storybook is a frontend workshop for building user interface components and pages in isolation. From 8.0.0 until 8.6.19, 9.1.21, 10.6.2, and 11.0.0-alpha.6, a malicious website can interact with the preview of a running Storybook development server. Insufficient iframe embedding and message-origin restrictions can allow attacker-controlled events to reach the running preview. A developer must visit the malicious website and interact with the injected interface. The attack can cause unauthorized changes to story files and, if a changed file is later executed by a local runtime, arbitrary code execution with the developer's privileges. This issue is fixed in 8.6.19, 9.1.21, 10.6.2, and 11.0.0-alpha.6."

Why Storybook admins should care

Severity scores use the Common Vulnerability Scoring System (CVSS). the address listed on github.com rated CVE-2026-114125 8.6 (High) under CVSS 4.0. Reading that rating in everyday terms: it can be reached over a network, including the internet; an attacker does not need an account; a user has to take a deliberate action. If it is abused, the rated damage to keeping data private is high, to keeping data unaltered is high, and to keeping Storybook running is high. Scoring string: CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:A/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X.

Affected Storybook releases

According to the record, these releases are vulnerable:

  • version >= 8.0.0, < 8.6.19
  • version >= 9.0.0, < 9.1.21
  • version >= 10.0.0, < 10.6.2
  • version >= 11.0.0-alpha.0, < 11.0.0-alpha.6

The type of bug behind CVE-2026-114125

NVD classifies it using MITRE's Common Weakness Enumeration:

  • CWE-94, Improper Control of Generation of Code. MITRE describes this class of bug as follows: "The product constructs all or part of a code segment using externally-influenced input from an upstream component, but it does not neutralize or incorrectly neutralizes special elements that could modify the syntax or behavior of the intended code segment. (Roles: Common-Name, Attack-Focused)"
  • CWE-346, Origin Validation Error. MITRE describes this class of bug as follows: "The product does not properly verify that the source of data or communication is valid."
  • CWE-1021, Improper Restriction of Rendered UI Layers or Frames. MITRE describes this class of bug as follows: "The web application does not restrict or incorrectly restricts frame objects or UI layers that belong to another application or domain."

Vendor remediation for CVE-2026-114125

The vendor advisory remediation for operators of Storybook, quoted for this page, is: "Update the storybook package to 8.6.19 (8.x), 9.1.21 (9.x), or 10.6.2 (10.x) or later, per GitHub security advisory GHSA-f2ph-cmg5-wxc8; related packages such as @storybook/core, @storybook/addon-vitest, and @storybook/addon-mcp have matching fixed releases."

What to do about it

  • Update now: Update the storybook package to 8.6.19 (8.x), 9.1.21 (9.x), or 10.6.2 (10.x) or later, per GitHub security advisory GHSA-f2ph-cmg5-wxc8; related packages such as @storybook/core, @storybook/addon-vitest, and @storybook/addon-mcp have matching fixed releases.
  • Who should act: IT teams, managed service providers, and developers who run or ship Storybook. Check every place it runs, including servers, build systems, containers, and older machines nobody watches closely.
  • Read the official advisory from Storybook (linked under Sources) for exact fixed builds and any temporary workaround if you cannot patch today.
  • After patching, confirm the new version is actually running and review logs from October 21, 2026 onward for anything unusual.
  • Home users: you do not need to buy or download anything because of CVE-2026-114125. A caller, text, or pop-up claiming your computer is "infected" with this CVE and asking for money or remote access is a scam.

CVE-2026-114125 record details from CISA and NVD

  • Attack complexity for CVE-2026-114125: low
  • CVE-2026-114125 attack requirements: none
  • Impact on connected systems: secrecy none, integrity none, availability none.
  • Who mapped the weakness type: the address listed on github.com (Secondary)
  • References in the NVD record: 11.
  • CISA SSVC decision points for CVE-2026-114125 (from NVD): exploitation=none; automatable=no; technicalImpact=total (role: CISA Coordinator, SSVC 2.0.3).

Dates to know

  • October 21, 2026: NVD publishes CVE-2026-114125.
  • October 31, 2026: FraudMeNot checks the CISA KEV catalog; CVE-2026-114125 is not listed.
  • October 28, 2026: most recent NVD update (record status: Awaiting Analysis).

Official references

Links listed in the NVD record (labels in brackets come from NVD):

Sources

General education only, not security advice. Facts checked against the sources above on the date shown.