storybookjs storybook Code Injection Flaw (CVE-2026-114125) Rated CVSS 8.6
A newly published high vulnerability in storybookjs storybook carries a CVSS score of 8.6. Here is what is affected and how to respond.
Key points
- CVE-2026-114125 affects storybookjs storybook.
- CVSS 8.6 (High).
- No exploitation confirmed yet.
storybookjs storybook is affected by CVE-2026-114125, a code injection that the National Vulnerability Database rates 8.6 out of 10.
At a glance
- CVE
- CVE-2026-114125
- Product
- storybookjs storybook
- CVSS
- 8.6 High
- Weakness
- code injection
- Exploited
- No known exploitation
What is the vulnerability?
The NVD entry states: 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.
Affected versions
| Vendor | Product | Versions |
|---|---|---|
| Storybookjs | storybook | >= 8.0.0, < 8.6.19, >= 9.0.0, < 9.1.21, >= 10.0.0, < 10.6.2, >= 11.0.0-alpha.0, < 11.0.0-alpha.6 |
Is it being exploited?
There is no public confirmation of exploitation at the time of publication. It does not appear in CISA's Known Exploited Vulnerabilities catalog. We will update this report if that changes.
What should you do?
- Identify whether the affected product and versions run in your environment.
- Apply the vendor update listed in the advisory as soon as it is available.
- Limit network exposure of the affected service until it is patched.
- Monitor the vendor advisory for updated guidance or exploitation reports.
What to do and how to stay safe: CVE-2026-114125
- Vulnerability severity scores ignore your specific architecture and context.
- Exploitability depends on network exposure and user behavior, not just code flaws.
- Prioritization requires continuous asset inventory and threat intelligence alignment.
Risk-based vulnerability management focuses your limited resources on the flaws that actually threaten your business. Start by mapping your critical assets and checking for active exploits to prioritize your backlog.
Step-by-step guide: Risk-Based Vulnerability Management: Prioritize Fixes by Actual Danger
General security guidance from the Threat Times newsroom. It is not confirmed advice from the organisations named in this story.
Frequently asked questions
What is CVE-2026-114125?
CVE-2026-114125 is a code injection vulnerability in storybookjs storybook.
How severe is CVE-2026-114125?
It has a CVSS score of 8.6 High.
Is CVE-2026-114125 being exploited?
There is no public confirmation of exploitation at the time of publication.
