Skip to main content
VulnerabilityPublished Updated

CVE-2026-19228: GitLab · Insecure Direct Object Reference

Affects gitlabSource GCVE Database

0
Compare

Not known to be exploited : upgrade to 19.2.2 or 19.1.4 soon.

Data as of 16 Nov 2026, 20:25 UTC

Severity
High

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

EPSS
0.3% chance of exploitation in 30 days – higher than 29% 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 16 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 should be applied by upgrading to GitLab EE versions 19.1.4 or later in the 19.1 series, or 19.2.2 or later in the 19.2 series. No additional mitigation steps are indicated by the vendor advisory.

Description

GitLab Enterprise Edition versions 19.1.0 through 19.1.3 and 19.2.0 through 19.2.1 contain an authorization bypass vulnerability. This flaw could allow an authenticated user to have AI usage incorrectly attributed to another namespace due to improper authorization of identity information in requests. The issue has been remediated in versions 19.1.4 and 19.2.2.

References

Community reviews

Loading reviews…