GitLab CE/EE affecting all · GitLab Has Remediated an Issue
Source GCVE Database
Not known to be exploited · CVSS 4.3 Medium · fixed in 19.5.6 : update GitLab when convenient.
Data as of 17 Nov 2026, 07:53 UTC
Thin evidence
One scorer or none| CNA (GitLab) | CVSS 3.1 | 4.3 |
|---|
- Patch
- Available – fixed in 19.5.6, 19.4.8, 19.3.9
CVSS:3.1/AV:N/AC:L/PR:L/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 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
|
GitHubgitlab-org/gitlabpkg:github/gitlab-org/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
GitLab has remediated this issue in versions 19.3.9, 19.4.8, and 19.5.6 and later. Users should upgrade affected GitLab CE/EE instances to these fixed versions or later to address the permission enforcement flaw. No other mitigation actions are indicated or required.
Description
A vulnerability in GitLab CE/EE versions from 17.8 before 19.3.9, 19.4 before 19.4.8, and 19.5 before 19.5.6 allowed authenticated users with planner-role permissions to set a future merge scheduling date on merge requests they authored. This capability should have been restricted to users with developer-role permissions or higher. The issue was due to insufficient permission enforcement on the merge scheduling field during merge request updates.