# CVE-2026-114125: Storybook: Missing origin validation in Storybook preview allows code injection from malicious websites - **Severity:** High 8.6 (`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`) - **Exploited in the wild:** Not known - **Fix available:** Yes - **Published:** 21 Oct 2026 - **Updated:** 28 Oct 2026 - **Also known as:** CLSA-2026-1793185389, GHSA-f2ph-cmg5-wxc8, ROOT-APP-NPM-CVE-2026-114125 ## What is CVE-2026-114125? CVE-2026-114125 is a high-severity vulnerability in storybookjs storybook, published on 21 Oct 2026. ### Official description 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. Weakness: CWE-94 (Improper Control of Generation of Code), CWE-346 (Origin Validation Error), CWE-1021 (Improper Restriction of Rendered UI Layers or Frames) ## Which versions are affected by CVE-2026-114125? 24 open source packages ship an affected version, including storybook, @storybook/addon-mcp and @storybook/addon-vitest. | Package | Ecosystem | Affected | Fixed in | | --- | --- | --- | --- | | `storybook` | npm | From 10.0.0 | 10.6.2 | | `storybook` | npm | From 10.0.0 | 10.6.2 | | `storybook` | npm | From 11.0.0-alpha.0 | 11.0.0-alpha.6 | | `storybook` | npm | From 11.0.0-alpha.0 | 11.0.0-alpha.6 | | `storybook` | npm | From 8.0.0 | 8.6.19 | | `storybook` | npm | From 8.0.0 | 8.6.19 | | `storybook` | npm | From 9.0.0 | 9.1.21 | | `storybook` | npm | From 9.0.0 | 9.1.21 | | `@storybook/addon-mcp` | npm | From 10.6.0 | 10.6.2 | | `@storybook/addon-mcp` | npm | From 10.6.0 | 10.6.2 | | `@storybook/addon-mcp` | npm | From 11.0.0-alpha.0 | 11.0.0-alpha.6 | | `@storybook/addon-mcp` | npm | From 11.0.0-alpha.0 | 11.0.0-alpha.6 | | `@storybook/addon-vitest` | npm | From 10.0.0 | 10.6.2 | | `@storybook/addon-vitest` | npm | From 10.0.0 | 10.6.2 | | `@storybook/addon-vitest` | npm | From 11.0.0-alpha.0 | 11.0.0-alpha.6 | | `@storybook/addon-vitest` | npm | From 11.0.0-alpha.0 | 11.0.0-alpha.6 | | `@storybook/addon-vitest` | npm | From 9.0.0 | 9.1.21 | | `@storybook/addon-vitest` | npm | From 9.0.0 | 9.1.21 | | `@storybook/core` | npm | From 8.0.0 | 8.6.19 | | `@storybook/core` | npm | From 8.0.0 | 8.6.19 | | `@storybook/core-server` | npm | From 8.0.0 | 8.6.19 | | `@storybook/core-server` | npm | From 8.0.0 | 8.6.19 | | `@storybook/experimental-addon-test` | npm | From 8.0.0 | 8.6.19 | | `@storybook/experimental-addon-test` | npm | From 8.0.0 | 8.6.19 | ## How do I fix CVE-2026-114125? Upgrade storybook to a fixed version for your release line: 10.6.2, 11.0.0-alpha.6, 8.6.19 or 9.1.21. ## Is CVE-2026-114125 being exploited? There is no known exploitation of CVE-2026-114125 in the wild and no public exploit code. ## Fix prompt for AI coding agents ```text Check this codebase for CVE-2026-114125 and fix it if it is affected. What it is: CVE-2026-114125 is a high-severity vulnerability in storybookjs storybook, published on 21 Oct 2026. Exploitation: There is no known exploitation of CVE-2026-114125 in the wild and no public exploit code. Affected packages and fixed versions: - storybook (npm): affected from 10.0.0; fixed in 10.6.2 - storybook (npm): affected from 10.0.0; fixed in 10.6.2 - storybook (npm): affected from 11.0.0-alpha.0; fixed in 11.0.0-alpha.6 - storybook (npm): affected from 11.0.0-alpha.0; fixed in 11.0.0-alpha.6 - storybook (npm): affected from 8.0.0; fixed in 8.6.19 - storybook (npm): affected from 8.0.0; fixed in 8.6.19 - storybook (npm): affected from 9.0.0; fixed in 9.1.21 - storybook (npm): affected from 9.0.0; fixed in 9.1.21 - @storybook/addon-mcp (npm): affected from 10.6.0; fixed in 10.6.2 - @storybook/addon-mcp (npm): affected from 10.6.0; fixed in 10.6.2 - @storybook/addon-mcp (npm): affected from 11.0.0-alpha.0; fixed in 11.0.0-alpha.6 - @storybook/addon-mcp (npm): affected from 11.0.0-alpha.0; fixed in 11.0.0-alpha.6 Task: 1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies. 2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it. 3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead. 4. Run the tests and summarise what changed and why. 5. If nothing in the project is affected, say so and change nothing. Reference: https://insights.sbomify.com/CVE-2026-114125/ (Markdown: https://insights.sbomify.com/CVE-2026-114125/index.md) ``` ## Sources - CVE record: https://www.cve.org/CVERecord?id=CVE-2026-114125 - NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-114125 - OSV: https://osv.dev/vulnerability/CVE-2026-114125 --- From sbomify Insights: https://insights.sbomify.com/CVE-2026-114125/ Summaries are generated and may contain mistakes; the official description above is the record.