Affects widely used GitLab CE/EE; stored XSS can enable session/token theft and account takeover across organizations.
CVE-2026-92883
Authenticated stored XSS in GitLab 19.x allowing script execution in other users' browsers
Is CVE-2026-92883 being exploited?
Not confirmed. CVE-2026-92883 does not appear in CISA's Known Exploited Vulnerabilities catalog, which records only exploitation that has been observed and reported publicly. That is evidence of absence of a report, not evidence the flaw is unattacked. EPSS currently estimates a 0.27% probability of exploitation in the next 30 days.
How severe is CVE-2026-92883?
CVE-2026-92883 is rated High with a CVSS score of 8.7. Severity describes how bad exploitation would be, not how likely it is: pair it with exploitation evidence before deciding what to patch first.
Is there a patch for CVE-2026-92883?
Yes. A fix has been recorded for CVE-2026-92883. The vendor advisory is the authority on the exact fixed version — apply it from there rather than from a summary.
What does CVE-2026-92883 affect?
CVE-2026-92883 affects GitLab CE/EE 19.1 up to <19.2.8, GitLab CE/EE 19.3 up to <19.3.5, GitLab CE/EE 19.4 up to <19.4.2. Confirm the exact affected versions against the vendor advisory before deciding you are exposed.
What should I do about CVE-2026-92883?
Upgrade to 19.2.8 / 19.3.5 / 19.4.2 immediately; review logs and rotate exposed tokens
Exploitation status reflects CISA's KEV catalog as we last synced it. Check the catalog directly.
Authenticated stored XSS via a crafted repository; attackers can run JS in victims' browsers to steal sessions/tokens, perform actions, or escalate access.
Immediate action required
- affected>= 19.1 and < 19.2.8
- affected>= 19.3 and < 19.3.5
- affected>= 19.4 and < 19.4.2
As published in the CVE Program record. A version outside these ranges is not a statement that it is unaffected — vendors sometimes understate a range, and distribution-backported builds carry upstream numbers that do not reflect what was patched into them.