storybook (npm) has 4 known vulnerabilities, the worst rated CRITICAL. Upgrade to 11.0.0-alpha.6 or later to clear all of them. No malicious-package signal is recorded.
Summary: A malicious website may be able to cause unauthorized file changes in a developer’s project while an affected Storybook development server is running.
CyberXYZ does not call a package safe in absolute terms. It records 4 known vulnerabilities for storybook (npm), the worst rated CRITICAL, and no malicious-package signal. Whether it is acceptable depends on the version you run.
Does storybook have known vulnerabilities?
Yes. CyberXYZ records 4 known vulnerabilities for storybook (npm), the worst rated CRITICAL. They are GHSA-f2ph-cmg5-wxc8, GHSA-px85-f4q5-jh77, GHSA-mjf5-7g4m-gx5w, GHSA-8452-54wp-rmv6.
Which version of storybook should I use?
11.0.0-alpha.6 or later clears every advisory recorded for storybook (npm). Check the release you pick before installing it.
How do I check storybook before installing?
Search storybook in CyberXYZ Check at https://cyberxyz.io/check?q=storybook. The xyz Scanner checks a project's dependencies, and CyberXYZ Proxy checks each package as it is installed.
Checked 2026-11-14 at 12:48 UTC. The most recent advisory here was published 2026-10-22. Updated continuously from NVD, GHSA, OSV and CNA feeds.