Skip to content

storybook-8.4.6.tgz: 2 vulnerabilities (highest severity is: 9.6) #178

@mend-bolt-for-github

Description

@mend-bolt-for-github
Vulnerable Library - storybook-8.4.6.tgz

Storybook's CLI - install, dev, build, upgrade, and more

Library home page: https://registry.npmjs.org/storybook/-/storybook-8.4.6.tgz

Path to dependency file: /package.json

Path to vulnerable library: /package.json

Vulnerabilities

Vulnerability Severity CVSS Dependency Type Fixed in (storybook version) Remediation Possible**
CVE-2026-27148 Critical 9.6 storybook-8.4.6.tgz Direct https://github.com/storybookjs/storybook.git - v9.1.19,https://github.com/storybookjs/storybook.git - v8.6.17,https://github.com/storybookjs/storybook.git - v7.6.23,https://github.com/storybookjs/storybook.git - v10.2.10
CVE-2025-68429 High 7.3 storybook-8.4.6.tgz Direct 8.6.15

**In some cases, Remediation PR cannot be created automatically for a vulnerability despite the availability of remediation

Details

CVE-2026-27148

Vulnerable Library - storybook-8.4.6.tgz

Storybook's CLI - install, dev, build, upgrade, and more

Library home page: https://registry.npmjs.org/storybook/-/storybook-8.4.6.tgz

Path to dependency file: /package.json

Path to vulnerable library: /package.json

Dependency Hierarchy:

  • storybook-8.4.6.tgz (Vulnerable Library)

Found in base branch: main

Vulnerability Details

Storybook is a frontend workshop for building user interface components and pages in isolation. Prior to versions 7.6.23, 8.6.17, 9.1.19, and 10.2.10, 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. 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 the 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. Both are vulnerable to injection via unsanitized input in the componentFilePath field, which can be exploited to achieve persistent XSS or Remote Code Execution (RCE). Versions 7.6.23, 8.6.17, 9.1.19, and 10.2.10 contain a fix for the issue.

Publish Date: 2026-02-25

URL: CVE-2026-27148

CVSS 3 Score Details (9.6)

Base Score Metrics:

  • Exploitability Metrics:
    • Attack Vector: Network
    • Attack Complexity: Low
    • Privileges Required: None
    • User Interaction: Required
    • Scope: Changed
  • Impact Metrics:
    • Confidentiality Impact: High
    • Integrity Impact: High
    • Availability Impact: High

For more information on CVSS3 Scores, click here.

Suggested Fix

Type: Upgrade version

Origin: GHSA-mjf5-7g4m-gx5w

Release Date: 2026-02-25

Fix Resolution: https://github.com/storybookjs/storybook.git - v9.1.19,https://github.com/storybookjs/storybook.git - v8.6.17,https://github.com/storybookjs/storybook.git - v7.6.23,https://github.com/storybookjs/storybook.git - v10.2.10

Step up your Open Source Security Game with Mend here

CVE-2025-68429

Vulnerable Library - storybook-8.4.6.tgz

Storybook's CLI - install, dev, build, upgrade, and more

Library home page: https://registry.npmjs.org/storybook/-/storybook-8.4.6.tgz

Path to dependency file: /package.json

Path to vulnerable library: /package.json

Dependency Hierarchy:

  • storybook-8.4.6.tgz (Vulnerable Library)

Found in base branch: main

Vulnerability Details

Storybook is a frontend workshop for building user interface components and pages in isolation. A vulnerability present starting in versions 7.0.0 and prior to versions 7.6.21, 8.6.15, 9.1.17, and 10.1.10 relates to Storybook’s handling of environment variables defined in a ".env" file, which could, in specific circumstances, lead to those variables being unexpectedly bundled into the artifacts created by the "storybook build" command. When a built Storybook is published to the web, the bundle’s source is viewable, thus potentially exposing those variables to anyone with access. For a project to potentially be vulnerable to this issue, it must build the Storybook (i.e. run "storybook build" directly or indirectly) in a directory that contains a ".env" file (including variants like ".env.local") and publish the built Storybook to the web. Storybooks built without a ".env" file at build time are not affected, including common CI-based builds where secrets are provided via platform environment variables rather than ".env" files. Storybook runtime environments (i.e. "storybook dev") are not affected. Deployed applications that share a repo with your Storybook are not affected. Users should upgrade their Storybook—on both their local machines and CI environment—to version .6.21, 8.6.15, 9.1.17, or 10.1.10 as soon as possible. Maintainers additionally recommend that users audit for any sensitive secrets provided via ".env" files and rotate those keys. Some projects may have been relying on the undocumented behavior at the heart of this issue and will need to change how they reference environment variables after this update. If a project can no longer read necessary environmental variable values, either prefix the variables with "STORYBOOK_" or use the "env" property in Storybook’s configuration to manually specify values. In either case, do not include sensitive secrets as they will be included in the built bundle.

Publish Date: 2025-12-17

URL: CVE-2025-68429

CVSS 3 Score Details (7.3)

Base Score Metrics:

  • Exploitability Metrics:
    • Attack Vector: Network
    • Attack Complexity: Low
    • Privileges Required: None
    • User Interaction: None
    • Scope: Unchanged
  • Impact Metrics:
    • Confidentiality Impact: Low
    • Integrity Impact: Low
    • Availability Impact: Low

For more information on CVSS3 Scores, click here.

Suggested Fix

Type: Upgrade version

Origin: GHSA-8452-54wp-rmv6

Release Date: 2025-12-17

Fix Resolution: 8.6.15

Step up your Open Source Security Game with Mend here

Metadata

Metadata

Assignees

No one assigned

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions