Skip to content

chore(deps): update dependency storybook to v10.2.10 [security]#1543

Open
renovate[bot] wants to merge 1 commit intomainfrom
renovate/npm-storybook-vulnerability
Open

chore(deps): update dependency storybook to v10.2.10 [security]#1543
renovate[bot] wants to merge 1 commit intomainfrom
renovate/npm-storybook-vulnerability

Conversation

@renovate
Copy link
Copy Markdown
Contributor

@renovate renovate bot commented Feb 26, 2026

This PR contains the following updates:

Package Change Age Confidence
storybook (source) 10.2.710.2.10 age confidence

GitHub Vulnerability Alerts

CVE-2026-27148

Summary

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.

Details

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 a 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, which can be exploited via unauthorized WebSocket connections to achieve persistent XSS or Remote Code Execution (RCE).

Note: recent versions of Chrome have some protections against this, but Firefox does not.

Impact

This vulnerability can lead to supply chain compromise. Key risks include:

  • Remote Code Execution: The vulnerability can allow attackers to execute malicious code, with the extent of impact depending on the configuration. Server-side RCE is possible in non-default configurations, such as when stories are executed via portable stories in JSDOM, potentially allowing attackers to exfiltrate credentials and environment variables, access source code and the filesystem, establish backdoors, or pivot to internal network resources.
  • Persistent XSS: Malicious payloads are written directly into story source files. If the malicious payload is committed to version control, it becomes part of the codebase and can propagate to deployed Storybook documentation sites, affecting developers and stakeholders who view them.
  • Supply Chain Propagation: If the modified source files are committed, injected code can spread to other team members via git, execute in CI/CD pipelines, and affect shared component libraries used across multiple projects.

Affected versions

8.1 and above. While the exploitable functionality was introduced in 8.1, the patch has been applied to 7.x as a precautionary measure given the underlying WebSocket behaviour.

Recommended actions

Update to one of the patched versions: 7.6.23, 8.6.17, 9.1.19, 10.2.10.


Release Notes

storybookjs/storybook (storybook)

v10.2.10

Compare Source

v10.2.9

Compare Source

v10.2.8

Compare Source


Configuration

📅 Schedule: Branch creation - "" (UTC), Automerge - At any time (no schedule defined).

🚦 Automerge: Enabled.

Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.

🔕 Ignore: Close this PR and you won't be reminded about this update again.


  • If you want to rebase/retry this PR, check this box

This PR was generated by Mend Renovate. View the repository job log.

@renovate renovate bot force-pushed the renovate/npm-storybook-vulnerability branch 6 times, most recently from 167ec84 to 2babdb8 Compare March 5, 2026 21:55
@renovate renovate bot force-pushed the renovate/npm-storybook-vulnerability branch 4 times, most recently from 3b2bd41 to c44c742 Compare March 11, 2026 12:55
@renovate renovate bot force-pushed the renovate/npm-storybook-vulnerability branch 4 times, most recently from 5a86b47 to 8983b22 Compare March 16, 2026 21:05
@renovate renovate bot force-pushed the renovate/npm-storybook-vulnerability branch 4 times, most recently from c3b32ad to d728e2b Compare March 26, 2026 22:04
@renovate renovate bot changed the title chore(deps): update dependency storybook to v10.2.10 [security] chore(deps): update dependency storybook to v10.2.10 [security] - autoclosed Mar 27, 2026
@renovate renovate bot closed this Mar 27, 2026
@renovate renovate bot deleted the renovate/npm-storybook-vulnerability branch March 27, 2026 01:11
@renovate renovate bot changed the title chore(deps): update dependency storybook to v10.2.10 [security] - autoclosed chore(deps): update dependency storybook to v10.2.10 [security] Mar 30, 2026
@renovate renovate bot reopened this Mar 30, 2026
@renovate renovate bot force-pushed the renovate/npm-storybook-vulnerability branch 4 times, most recently from abc035c to 3909b97 Compare April 1, 2026 20:51
@renovate renovate bot force-pushed the renovate/npm-storybook-vulnerability branch 3 times, most recently from 809c98a to 087841c Compare April 9, 2026 23:09
@renovate renovate bot force-pushed the renovate/npm-storybook-vulnerability branch from 087841c to 51a713d Compare April 9, 2026 23:13
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

0 participants