CVE-2026-122226: GitLab · Improper Cleanup on Thrown Exception
Affects GitLabSource CVE Database V5
Not known to be exploited · CVSS 2.2 Low · 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 | 2.2 |
|---|
- Patch
- Available – fixed in 19.5.6, 19.4.8, 19.3.9
CVSS:3.1/AV:N/AC:H/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 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 affected GitLab EE instances to versions 19.3.9, 19.4.8, or 19.5.6 or later where the issue is fixed. Since this is a low-severity issue and a fix is available, applying the official patches is the recommended mitigation. No additional vendor advisories indicate alternative mitigations or that no action is required.
Description
CVE-2026-122226 is a low-severity vulnerability in GitLab EE that affects versions from 18.8 up to but not including 19.3.9, 19.4 up to 19.4.8, and 19.5 up to 19.5.6. The issue involves improper cleanup on thrown exceptions (CWE-460) which could allow an authenticated user to access GitLab Duo features that should be restricted by group-based access rules. This occurs due to improper handling of failed updates to those access rules. GitLab has fixed this vulnerability in versions 19.3.9, 19.4.8, and 19.5.6.