GitLab CE/EE affecting all · GitLab Has Remediated an Issue
Source GCVE Database
Not known to be exploited · CVSS 7.1 High · fixed in 19.2.4 : patch affected systems soon.
Data as of 15 Nov 2026, 20:25 UTC
- EPSS
- 0.2% chance of exploitation in 30 days – higher than 11% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
- Patch
- Available – fixed in 19.2.4, 19.1.6, 19.0.8 +1
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:H/A:LExploitation evidence
Disclosed: evidence found.
CVE published 17 Aug 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: evidence found.
Public exploit code: GitHub proofs of concept
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), GitHub proofs of concept, the Metasploit, Exploit-DB and nuclei-templates index as of 15 Nov 2026.
What to do
AI-suggested
Upgrade GitLab CE/EE to versions 18.11.11 or later for the 18.2 series, 19.0.8 or later for the 19.0 series, 19.1.6 or later for the 19.1 series, and 19.2.4 or later for the 19.2 series. These versions contain the official fix for this vulnerability. No additional mitigations are indicated.
Description
A vulnerability in GitLab CE/EE versions from 18.2 before 18.11.11, 19.0 before 19.0.8, 19.1 before 19.1.6, and 19.2 before 19.2.4 allowed unauthenticated users to execute mutations via GET requests due to improper request validation in GraphQL multiplex query handling. This issue has been remediated by GitLab.