This is a stored XSS vulnerability in GitLab's analytics dashboard where malicious payload executes through pagination controls. The critical insight is that pagination components occupy a security-relevant position that most teams overlook — they render within authenticated analytics contexts that aggregate access across projects, users, and integrations. An XSS payload executing there inherits a privileged session with cross-project visibility, making this far more severe than a comment-field XSS that affects only the commenter. The vulnerability likely originated from a refactor that attached a new data source to an existing pagination component whose prior inputs happened to be trusted, rather than from someone writing unsafe code directly. Check your own analytics dashboards for pagination components that render data from multiple sources, particularly those aggregating user identifiers, project names, or query parameters. Audit the data pipeline feeding those components — the fix isn't just patching the rendering call but ensuring sanitization occurs at every trust boundary the data crosses. The component library you use likely carries forward implicit trust assumptions from when analytics dashboards were simpler internal tools; treat pagination controls on modern analytics surfaces as session-context boundaries requiring the same scrutiny as authentication surfaces. If your organization has shared pagination components, ensure the security boundary is embedded in the component itself rather than assumed at each usage site — patching individual instances won't close the class if the underlying component trusts its inputs by default.
CVE-2026-15216
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedGitLab has remediated an issue in GitLab CE/EE affecting all versions from 18.2 before 19.0.6, 19.1 before 19.1.4, and 19.2 before 19.2.2 that under certain conditions could have allowed cross-site scripting due to improper neutralization of user-controlled data rendered in pagination controls by an analytics dashboard component.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysisUntrusted input is placed into a web page without being neutralised, so an attacker's markup or script executes in another user's browser. That can hijack sessions, capture keystrokes, or silently perform actions as the victim. Fixing it properly means context-aware output encoding everywhere data meets HTML, backed by a content-security policy as a second line of defence.
General guidance for the cross-site scripting (xss) class — the official description and references above are authoritative for this specific CVE. Want a bespoke review and a reviewed fix? Ask our team →
CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Network
- Complexity
- Low
- Privileges
- Low
- User interaction
- Required
- Scope
- Changed
- Confidentiality
- High
- Integrity
- High
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:C/C:H/I:H/A:N
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
dbcve · scopedGitLab 19.0.6 (for 18.2-19.0.x), 19.1.4 (for 19.1.x), or 19.2.2 (for 19.2.x) - or latest stable 19.3+
- 1. Identify the currently installed GitLab version by running `sudo gitlab-rake gitlab:env:info` or checking the admin area
- 2. Determine which version branch you are on (18.2-19.0.x, 19.1.x, or 19.2.x)
- 3. For 18.2-19.0.x branch: Upgrade to GitLab 19.0.6 or later
- 4. For 19.1.x branch: Upgrade to GitLab 19.1.4 or later
- 5. For 19.2.x branch: Upgrade to GitLab 19.2.2 or later
- 6. Alternatively, upgrade to the latest stable GitLab release (19.3 or later) which contains all security fixes
- 7. After upgrade, verify the analytics dashboard pagination controls no longer execute unsanitized user input
Generated from the published advisory — verify against the referenced sources before acting.
There is no version to upgrade to and no patch to apply. Every affected install stays exposed until the vendor ships a fix — or somebody else builds one.
Free. We build fixes in the order the community asks for them — and we’ll tell you the moment this one lands.
We develop and verify an original fix where the vendor hasn’t, from $3,100. Deployed to your staging first — never straight to production.
Scope it with usSee what else the community needs solved on the solutions-needed board.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-15216 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesThis is a stored XSS vulnerability in GitLab's analytics dashboard where malicious payload executes through pagination controls. The critical insight is that pagination components occupy a security-relevant position that most teams overlook — they render within authenticated analytics contexts that aggregate access across projects, users, and integrations. An XSS payload executing there inherits a privileged session with cross-project visibility, making this far more severe than a comment-field XSS that affects only the commenter. The vulnerability likely originated from a refactor that attached a new data source to an existing pagination component whose prior inputs happened to be trusted, rather than from someone writing unsafe code directly. Check your own analytics dashboards for pagination components that render data from multiple sources, particularly those aggregating user identifiers, project names, or query parameters. Audit the data pipeline feeding those components — the fix isn't just patching the rendering call but ensuring sanitization occurs at every trust boundary the data crosses. The component library you use likely carries forward implicit trust assumptions from when analytics dashboards were simpler internal tools; treat pagination controls on modern analytics surfaces as session-context boundaries requiring the same scrutiny as authentication surfaces. If your organization has shared pagination components, ensure the security boundary is embedded in the component itself rather than assumed at each usage site — patching individual instances won't close the class if the underlying component trusts its inputs by default.
Practitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2026-15216 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data