Database/Control plane, storage & DevOps
GitLab: cross-site scripting in Error Tracking pages
Impact
An authenticated user can get JavaScript to run in the browser of anyone viewing Error Tracking pages, with that viewer's GitLab session. If the viewer is a maintainer or admin, the script can reach CI/CD settings and the deploy credentials GitLab holds. This is a separate code path from the wiki XSS fixed in the same release.
Who can reach it
Remote, authenticated GitLab user. A victim has to view the affected Error Tracking page.
What to do
Upgrade self-managed GitLab to 19.3.9, 19.4.8 or 19.5.6 or later. This is a GitLab service upgrade and restart. Affected versions go back to 16.1.
References
Related entries
- Semaphore UI: task_runner users override Ansible connection vars to run code as the server userCVE-2026-112305 · Semaphore UI (task environment JSON -> Ansible variable override)High
- Temporal Server: k8s compute provider builds a client from caller input, running commands on the Worker Service hostCVE-2026-120091 · Temporal Server Worker Service (go.temporal.io/auto-scaled-workers k8s compute provider)High
- Grid Community Toolkit globus-gss-assist: pre-auth heap out-of-bounds write via short SSLv2 GSI recordCVE-2026-123975 · Grid Community Toolkit globus-gss-assist (GSI handshake token reader)High
- GitLab CE/EE: stored XSS in analytics dashboard pagination controlsCVE-2026-15216 · GitLab CE/EE (analytics dashboard pagination controls)High
- GitLab CE/EE: stored XSS in analytics dashboard table cell renderingCVE-2026-15217 · GitLab CE/EE (analytics dashboard table cell rendering)High
- Sigstore Fulcio: OIDC discovery follows cross-host redirects and leaks ServiceAccount tokensCVE-2026-49478 · Sigstore Fulcio (OIDC discovery HTTP client, cross-host redirects)High
This entry is curated: imported from vendor advisories with machine assistance, not yet individually verified. Confirm against your vendor's advisory before acting, and report anything wrong.