Skip to main content
CVE-2026-18244VulnerabilityPublished

GitLab EE affecting all · GitLab Has Remediated an Issue

Source GCVE Database

0
Compare

Not known to be exploited · CVSS 4.3 Medium · fixed in 19.2.2 : update affected systems when convenient.

Data as of 11 Nov 2026, 23:24 UTC

CVSS 3.1 base score
4.3Medium
How severe the flaw is on the 0–10 CVSS scale.
EPSS
0.2% chance of exploitation in 30 days – higher than 20% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
Patch
Available – fixed in 19.2.2, 19.1.4, 19.0.6
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:N/A:N

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 12 Aug 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 11 Nov 2026.

What to do

AI-suggested

Upgrade GitLab EE to version 19.0.6, 19.1.4, or 19.2.2 or later to remediate this vulnerability. Applying these official fixes fully addresses the issue.

Description

A vulnerability in GitLab EE versions from 17.7 before 19.0.6, 19.1 before 19.1.4, and 19.2 before 19.2.2 could allow an authenticated user to view restricted configuration settings due to improper authorization checks on a group settings page. This issue has been remediated by GitLab in the specified fixed versions.

References

Community reviews

Loading reviews…