storybookjs Storybook up to 8.6.18/9.1.20/10.6.1/11.0.0-alpha.5 Development Server code injection

Summaryinfo

A vulnerability identified as critical has been detected in storybookjs Storybook up to 8.6.18/9.1.20/10.6.1/11.0.0-alpha.5. This issue affects some unknown processing of the component Development Server. Performing a manipulation results in code injection. This vulnerability was named CVE-2026-114126. The attack may be initiated remotely. There is no available exploit. You should upgrade the affected component.

Detailsinfo

A vulnerability was found in storybookjs Storybook up to 8.6.18/9.1.20/10.6.1/11.0.0-alpha.5. It has been classified as critical. This affects some unknown functionality of the component Development Server. The manipulation with an unknown input leads to a code injection vulnerability. CWE is classifying the issue as CWE-94. 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. This is going to have an impact on confidentiality, integrity, and availability. The summary by CVE is:

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, the Storybook development server can expose its WebSocket authentication token to clients able to load its HTML pages over a local network. A LAN attacker can obtain the token and invoke WebSocket-backed file-writing or testing functionality. Weak story-write validation can allow code to be placed in story files. If the Storybook Vitest addon is installed with an old version of Vitest, the payload can use a Vitest API to write additional files or execute commands. Depending on the payload and local tooling, the attack can lead to 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.

It is possible to read the advisory at github.com. This vulnerability is uniquely identified as CVE-2026-114126 since 10/20/2026. The exploitability is told to be easy. It is possible to initiate the attack remotely. No form of authentication is needed for exploitation. It demands that the victim is doing some kind of user interaction. The technical details are unknown and an exploit is not publicly available. The attack technique deployed by this issue is T1059 according to MITRE ATT&CK.

Upgrading to version 8.6.19, 9.1.21, 10.6.2 or 11.0.0-alpha.6 eliminates this vulnerability.

Statistical analysis made it clear that VulDB provides the best quality for vulnerability data.

Productinfo

Vendor

• storybookjs

Name

• Storybook

Version

• 8.6.0
• 8.6.1
• 8.6.2
• 8.6.3
• 8.6.4
• 8.6.5
• 8.6.6
• 8.6.7
• 8.6.8
• 8.6.9
• 8.6.10
• 8.6.11
• 8.6.12
• 8.6.13
• 8.6.14
• 8.6.15
• 8.6.16
• 8.6.17
• 8.6.18
• 9.1.0
• 9.1.1
• 9.1.2
• 9.1.3
• 9.1.4
• 9.1.5
• 9.1.6
• 9.1.7
• 9.1.8
• 9.1.9
• 9.1.10
• 9.1.11
• 9.1.12
• 9.1.13
• 9.1.14
• 9.1.15
• 9.1.16
• 9.1.17
• 9.1.18
• 9.1.19
• 9.1.20
• 10.6.0
• 10.6.1
• 11.0.0-alpha.0
• 11.0.0-alpha.1
• 11.0.0-alpha.2
• 11.0.0-alpha.3
• 11.0.0-alpha.4
• 11.0.0-alpha.5

Website

• Product: https://github.com/storybookjs/storybook/

CPE 2.3info

• 🔒
• 🔒
• 🔒

CPE 2.2info

• 🔒
• 🔒
• 🔒

CVSSv4info

CVSSv3info

CVSSv2info

Exploitinginfo

Threat Intelligenceinfo

Countermeasuresinfo

Timelineinfo

Sourcesinfo

Entryinfo

Statistical analysis made it clear that VulDB provides the best quality for vulnerability data.

Discussion