Skip to main content
VulnerabilityPublished

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

Affects GitLabSource GCVE Database

0
Compare

Not known to be exploited · CVSS 4.3 Medium · fixed in 18.9.7 : update GitLab when convenient.

Data as of 11 Nov 2026, 23:18 UTC

CVSS 3.1 base score
4.3Medium
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.14.3
Patch
Available – fixed in 18.9.7
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:L/A:N

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 14 May 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

Affected software

ProductAffectedFixed in
GitLab GitLabAffected
  • =11.10
  • =18.10
  • =18.11
Fixed in–

AI-suggested

This vulnerability has been officially fixed in GitLab EE versions 18.9.7, 18.10.6, and 18.11.3. Users should upgrade to these or later versions to remediate the issue. No additional mitigation steps are required beyond applying the official patches.

Description

CVE-2026-6063 is an authorization bypass vulnerability in GitLab EE versions 11.10, 18.10, and 18.11 prior to fixed releases. It allows an authenticated user with developer-role permissions to remove code owner approval rules from merge requests due to improper access control. The issue has been remediated in GitLab EE versions 18.9.7, 18.10.6, and 18.11.3.

References

Community reviews

Loading reviews…