CVE-2026-123142: GitLab · Incorrect Authorization
Affects GitLabSource CVE Database V5
Not known to be exploited · CVSS 4.3 Medium · fixed in 19.5.6 : update GitLab when convenient.
Data as of 17 Nov 2026, 04:35 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
|
CPE configurations (1)
cpe:2.3:a:gitlab:gitlab:*:*:*:*:*:*:*:*
AI-suggested
Upgrade GitLab CE/EE installations to version 19.3.9, 19.4.8, or 19.5.6 or later to remediate this vulnerability. No additional mitigations are indicated as the issue is fixed in these official releases.
Description
An authorization flaw in GitLab CE/EE versions from 18.4 up to but not including 19.3.9, 19.4 up to 19.4.8, and 19.5 up to 19.5.6 allowed authenticated users with MCP-scoped OAuth tokens to perform unauthorized state changes on issues and merge requests, including approving and merging. This issue has been fixed in versions 19.3.9, 19.4.8, and 19.5.6.