Skip to main content
CVE-2026-115219VulnerabilityPublished

GitLab EE affecting all · GitLab Has Remediated an Issue

Source GCVE Database

0
Compare
Authoritative record:CVE-2026-115219· Low 3.8

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

Data as of 17 Nov 2026, 07:53 UTC

CVSS 3.1 base score
3.8Low
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.13.8
Patch
Available – fixed in 19.5.6, 19.4.8, 19.3.9
CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:L/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 and gitlab-org/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
  • >=19.2 <19.3.9
Fixed in
  • 19.3.9
GitHubgitlab-org/gitlabpkg:github/gitlab-org/gitlabOther threatsAffected
  • >=19.2 <19.3.9
  • >=19.4 <19.4.8
  • >=19.5 <19.5.6
Fixed in
  • 19.3.9
  • 19.4.8
  • 19.5.6

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 versions 19.3.9, 19.4.8, or 19.5.6 or later where the issue is fixed. Since the vulnerability is remediated in these releases, applying the official patches is the recommended action.

Description

A vulnerability in GitLab Enterprise Edition versions from 19.2 up to but not including 19.3.9, 19.4 up to but not including 19.4.8, and 19.5 up to but not including 19.5.6 allowed authenticated users to enable Amazon Q automatic code reviews on projects despite administrator locks. This occurred due to improper enforcement of instance-level settings. The issue has been remediated in versions 19.3.9, 19.4.8, and 19.5.6.

References

Community reviews

Loading reviews…