CVE-2026-103515: GitLab · Incorrect Authorization
Affects GitLabSource CVE Database V5
Not known to be exploited · CVSS 2.7 Low · fixed in 19.5.1 : update GitLab when convenient.
Data as of 26 Oct 2026, 13:07 UTC
- EPSS
- 0.2% chance of exploitation in 30 days – higher than 13% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
- Patch
- Available – fixed in 19.5.1, 19.4.3, 19.3.6
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 21 Oct 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: 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 26 Oct 2026.
What to do
Upgrade GitLab to 19.5.1, 19.4.3 or 19.3.6.
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:*:*:*:*:*:*:*:*
Description
GitLab has remediated an issue in GitLab EE affecting all versions from 19.2 before 19.3.6, 19.4 before 19.4.3, and 19.5 before 19.5.1 that, when an instance administrator locked a group's Duo availability, an authenticated user with group Owner permissions could have re-enabled AI-backed data egress to a third-party service for that group and its descendant projects, due to insufficient granularity of the admin-lock enforcement controls.