CVE-2026-5262 is a cross-site scripting vulnerability in GitLab CE/EE affecting the Storybook development environment. It affects all versions from 16.1.0 before 18.9.6, 18.10 before 18.10.4, and 18.11 before 18.11.1. The issue is caused by improper input validation and insufficient sanitization of user-supplied input rendered within the Storybook integration, allowing attacker-controlled script execution in a victim’s browser under certain conditions. Because scripts execute in the Storybook context, they can access sensitive tokens present in that development environment and potentially expose them for further misuse.
Mallory correlates every CVE against your assets, your vendors, and active adversary campaigns. Know which vulnerabilities matter for you, not just which ones are loud.
What it means. What to do now. Patch path, mitigations, and the assume-compromise checklist.
What an attacker gets, and what they’ve been doing with it.
If you can’t patch tonight, do this now.
Patch, then assume compromise.
No public exploits tracked yet. Mallory keeps watching.
No public exploit code observed for this vulnerability.
Products and vendors Mallory has correlated with this vulnerability. Open in Mallory to drill down to specific CPE configurations and version ranges.
Vendor-confirmed product mapping. Mallory continuously reconciles this list against your asset inventory.
9 sources tracked across advisories, community write-ups, and news. New activity surfaces here as Mallory finds it.
An improper input validation vulnerability in GitLab CE/EE that could allow an unauthenticated user to access tokens in the Storybook development environment under certain conditions.
A high-severity cross-site scripting vulnerability in GitLab's Storybook development environment that can expose sensitive tokens to unauthenticated attackers, potentially enabling authenticated access to broader GitLab resources.
Query your assets running an affected version, and investigate the blast radius.
Every observed campaign linking this CVE to a named adversary.
Malware families riding this exploit, with evidence and IOCs.
YARA, Sigma, Snort, and vendor rules, auto-deployed to your SIEM.
Cross-references every affected SKU, including bundled OEM variants.
Community discussion across Reddit, Mastodon, and other social sources.