CVE-2026-4922: GitLab · Cross-Site Request Forgery
Affects GitLabSource GCVE Database
Not known to be exploited · CVSS 8.1 High · fixed in 18.11.1 : patch GitLab soon.
Data as of 12 Nov 2026, 00:47 UTC
Thin evidence
One scorer or none| CNA (GitLab) | CVSS 3.1 | 8.1 |
|---|
- Patch
- Available – fixed in 18.11.1, 18.10.4, 18.9.6
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:NExploitation evidence
Disclosed: evidence found.
CVE published 22 Apr 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors
A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 11 Nov 2026.
What to do
Upgrade GitLab to 18.11.1, 18.10.4 or 18.9.6.
Affected software
| Product | Affected | Fixed in |
|---|---|---|
RubyGemsgitlabpkg:gem/gitlabOther threats | Affected
| Fixed in
|
Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.
AI-suggested
Upgrade affected GitLab CE/EE instances to versions 18.9.6, 18.10.4, or 18.11.1 or later where the vulnerability has been fixed. Since this is a software vulnerability with an official fix, applying the vendor's patches is the recommended mitigation. No additional mitigations are specified.
Description
CVE-2026-4922 is a high-severity Cross-Site Request Forgery (CSRF) vulnerability in GitLab CE/EE. It affects all versions from 17.0 before 18.9.6, 18.10 before 18.10.4, and 18.11 before 18.11.1. The flaw could allow an unauthenticated attacker to execute GraphQL mutations on behalf of authenticated users due to insufficient CSRF protections.