Skip to main content
VulnerabilityPublished Updated

CVE-2026-18433: GitLab · Incorrect Authorization

Affects gitlabSource GCVE Database

0
Compare

Not known to be exploited : upgrade to 19.2.2 or 19.1.4 when convenient.

Data as of 17 Nov 2026, 20:25 UTC

Severity
Medium

Rated by Threat Radar · No CVSS score from NVD or the CNA

EPSS
0.3% chance of exploitation in 30 days – higher than 33% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
Patch
Available – fixed in 19.2.2, 19.1.4

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 18 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 17 Nov 2026.

What to do

Upgrade gitlab to 19.2.2 or 19.1.4.

Affected software

ProductAffectedFixed in
Bitnamigitlabpkg:bitnami/gitlabOther threatsAffected
  • >=19.1.0 <19.1.4
  • >=19.2.0 <19.2.2
Fixed in
  • 19.1.4
  • 19.2.2

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

AI-suggested

A patch is available and has been released in GitLab EE versions 19.1.4 and 19.2.2. Users should upgrade affected installations to these or later versions to remediate the vulnerability. No additional mitigation steps are indicated by the vendor.

Description

GitLab Enterprise Edition versions 19.1.0 through 19.1.3 and 19.2.0 through 19.2.1 contain an incorrect authorization vulnerability in a GraphQL query. This flaw could allow an authenticated user to read policy configuration data belonging to namespaces they are not authorized to access. The issue has been remediated in versions 19.1.4 and 19.2.2. No known exploits are reported in the wild.

References

Community reviews

Loading reviews…