Skip to main content
Mallory
MediumVulnerability

CVE-2026-5262: Cross-site scripting in GitLab Storybook development environment

Published Apr 22, 2026 · Updated 2 months ago
Trending this weekNot trendingOutside this week’s top 100
Mention activity · 30 daysNo mention activity in the last 30 days.
CVSS6.1Medium · v3.1
EPSS0.22%13th percentile
CISA KEVNoNot listed
In the wildNoneNo exploitation reported
Vendor
GitLab
IdentifiersCVE-2026-5262CWE-79 · Improper Neutralization of Input…

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.

Do you run this?See affected versions in your environment and whether adversaries are exploiting this vulnerability against assets like yours.
Check your exposure
Analyst brief

Impact, mitigation & remediation

What it means and what to do now: patch path, interim mitigations, and the assume-compromise checklist.

Impact

What an attacker gets, and what they’ve been doing with it.

Successful exploitation allows an unauthenticated remote attacker to execute malicious script in a victim’s browser session within the Storybook context and obtain sensitive tokens exposed there. Those tokens may then be used to access other GitLab services or APIs, resulting in high confidentiality and integrity impact. No direct availability impact has been documented.

Mitigation

If you can’t patch tonight, do this now.

No vendor-documented temporary workaround or configuration-based mitigation has been identified. Where immediate upgrade is not possible, exposure can only be reduced operationally by limiting access to affected instances and minimizing opportunities for users to open untrusted links or attacker-controlled content, but definitive mitigation requires upgrading to a patched release.

Remediation

Patch, then assume compromise.

Upgrade GitLab CE/EE to a fixed release: 18.9.6 or later for affected 16.1.x through 18.9.x deployments, 18.10.4 or later for affected 18.10.x deployments, or 18.11.1 or later for affected 18.11.x deployments. Self-managed installations require manual upgrade to a patched version. GitLab.com was already running a remediated version at disclosure time.

Public exploits

Exploits

No public exploits tracked yet. Mallory keeps watching.

View more in app →
No public exploit code observed for this vulnerability. Mallory keeps watching.
Exposure surface

Affected products & vendors

Products and vendors Mallory has correlated with this vulnerability. Open in Mallory to drill down to specific CPE configurations and version ranges.

VendorProductType
GitLabGitlabapplication
FAQ

Frequently asked questions

Is CVE-2026-5262 exploited in the wild?
As of Sep 25, 2026, Mallory has no reports of CVE-2026-5262 being exploited in the wild. It is not listed in CISA KEV.
Is there a public exploit for CVE-2026-5262?
As of Sep 25, 2026, Mallory has found no public exploit for CVE-2026-5262.
Is there a patch for CVE-2026-5262?
Upgrade GitLab CE/EE to a fixed release: 18.9.6 or later for affected 16.1.x through 18.9.x deployments, 18.10.4 or later for affected 18.10.x deployments, or 18.11.1 or later for affected 18.11.x deployments. Self-managed installations require manual upgrade to a patched version.
What products are affected by CVE-2026-5262?
Gitlab.
How severe is CVE-2026-5262?
CVE-2026-5262 has a CVSS v3.1 score of 6.1 (Medium) and an EPSS score of 0.22% (13th percentile) as of Sep 25, 2026.
Mallory platform

The version that knows your environment.

This page is what’s public. Mallory adds the parts that aren’t: which of your assets are affected, which adversaries are exploiting it right now, and which detections to deploy tonight.
Exposure mappingQuery your assets running an affected version, and investigate the blast radius.
Threat actor evidenceEvery report linking this CVE to a named adversary.
Associated malwareMalware families linked to this CVE, with evidence and IOCs.
Detection signaturesYARA, Sigma, Snort, and vendor rules, auto-deployed to your SIEM.
Vendor-by-vendor mappingCross-references every affected SKU, including bundled OEM variants.
Social activity5Community discussion across Reddit, Mastodon, and other social sources.