Skip to main content
CVE-2026-122226VulnerabilityPublished

GitLab EE affecting all · GitLab Has Remediated an Issue

Source GCVE Database

0
Compare
Authoritative record:CVE-2026-122226· Low 2.2

Not known to be exploited · CVSS 2.2 Low · fixed in 19.5.6 : update GitLab when convenient.

Data as of 17 Nov 2026, 08:04 UTC

CVSS 3.1 base score
2.2Low
How severe the flaw is on the 0–10 CVSS scale.

Thin evidence

One scorer or none
CVSS scores by source
CNA (GitLab)CVSS 3.12.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:N

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 17 Nov 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponized: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq 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

ProductAffectedFixed in
GitLabGitLabAffected
  • >=19.5 <19.5.6
Fixed in
  • 19.5.6
GitLabGitLabAffected
  • >=19.4 <19.4.8
Fixed in
  • 19.4.8
GitLabGitLabAffected
  • >=18.8 <19.3.9
Fixed in
  • 19.3.9

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 version from 18.8 before 19.3.9; to 19.4.8 or later if running a version from 19.4 before 19.4.8; or to 19.5.6 or later if running a version from 19.5 before 19.5.6. These versions contain the official fix for this vulnerability.

Description

A vulnerability in GitLab EE versions from 18.8 before 19.3.9, 19.4 before 19.4.8, and 19.5 before 19.5.6 could allow an authenticated user to access GitLab Duo features restricted by group-based access rules. This occurs due to improper handling of failed updates to those rules. The issue has been remediated in the specified fixed versions.

References

Community reviews

Loading reviews…