GitLab EE affecting all · GitLab Has Remediated an Issue
Source GCVE Database
Not known to be exploited · CVSS 2.7 Low · fixed in 19.5.6 : update GitLab when convenient.
Data as of 17 Nov 2026, 07:52 UTC
Thin evidence
One scorer or none| CNA (GitLab) | CVSS 3.1 | 2.7 |
|---|
- Patch
- Available – fixed in 19.5.6, 19.4.8, 19.3.9
CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:N/I:L/A:NExploitation evidence
Disclosed: evidence found.
CVE published 17 Nov 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 16 Nov 2026.
What to do
Upgrade GitLab and gitlab/gitlab to 19.5.6, 19.4.8 or 19.3.9.
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| GitLabGitLab | Affected
| Fixed in
|
| GitLabGitLab | Affected
| Fixed in
|
| GitLabGitLab | Affected
| Fixed in
|
RubyGemsgitlab/gitlabpkg:gem/gitlab/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 GitLab EE to version 19.3.9 or later if running a 19.3.x branch, 19.4.8 or later if running a 19.4.x branch, or 19.5.6 or later if running a 19.5.x branch. These versions contain the official fix for this authorization issue.
Description
A vulnerability in GitLab EE versions from 19.2 before 19.3.9, 19.4 before 19.4.8, and 19.5 before 19.5.6 allowed an authenticated user to change the GitLab Duo Code Review consent setting of a parent group due to incorrect authorization checks. This issue has been remediated by GitLab.