dbcve.org
GitLabApplication

CVE-2026-6269

MEDIUM · 5.4 CVSS v3.1 Published 2026-06-11
Fix available
A fix is available. Upgrade to 18.10.8 / 18.11.5 or later.
See remediation →
60/100
Remediation priority · Elevated
Remotely reachable Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
GitLab has remediated an issue in GitLab CE/EE affecting all versions from 15.10 before 18.10.8, 18.11 before 18.11.5, and 19.0 before 19.0.2 that under certain conditions could have allowed an authenticated user with developer-role permissions to modify hidden merge requests due to incorrect authorization enforcements.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

GitLab CE/EE had an authorization bypass where authenticated users with developer-role permissions could modify hidden merge requests they should not have access to, due to incorrect authorization enforcement logic.

MitigationUpgrade GitLab to version 18.10.8 and later, 18.11.5 and later, or 19.0.2 and later to apply the patched release.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
GitLabApplication
Affected:>= 15.10.0, < 18.10.8>= 18.11.0, < 18.11.5>= 19.0.0, < 19.0.2

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
Low
User interaction
None
Scope
Unchanged
Confidentiality
Low
Integrity
Low
Availability
None

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:L/A:N

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Identify installed GitLab version
    Run `sudo gitlab-rake gitlab:env:info` or check the GitLab admin panel under Help > Version. Alternatively, check the /opt/gitlab/version file.
    Affected if Version falls within >= 15.10.0 and < 18.10.8, OR >= 18.11.0 and < 18.11.5, OR >= 19.0.0 and < 19.0.2
  2. Verify hidden merge requests feature is in use
    Check if any projects have merge requests with the hidden/collapsed discussion setting enabled. In GitLab UI, navigate to a project's Merge Requests and look for MRs with hidden comments or navigate to Project Settings > Merge Requests to review settings.
    Affected if Hidden merge requests exist in the GitLab instance
  3. Review developer role assignments
    Check user memberships in projects or groups. Use GitLab API: `GET /projects/:id/members/all` or navigate to Project > Settings > Members to list users with Developer role.
    Affected if Users with Developer role exist who should not have access to certain hidden merge requests
  4. Audit merge request authorization logs
    Review GitLab audit logs for merge request update events. Use the UI: Admin Area > Monitoring > Audit Events, or API: `/audit_events?entity_type=MergeRequest&action=update`. Look for unauthorized modifications.
    Affected if Audit logs show merge request modifications by users without proper access

You are affected if your GitLab version is within the vulnerable ranges AND hidden merge requests exist in your instance with users who may have had unintended write access.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Upgrade available Upgrade to 18.10.8 / 18.11.5 / 19.0.2 or later
Fixed in 18.10.818.11.519.0.2
Interim mitigation

Upgrade GitLab to version 18.10.8 and later, 18.11.5 and later, or 19.0.2 and later to apply the patched release.

Recommended fix High confidence

Upgrade to GitLab 18.10.8, 18.11.5, or 19.0.2 or later (preferably latest stable 18.x or 19.x)

  1. 1. Back up your GitLab instance data before proceeding with the upgrade
  2. 2. Review GitLab upgrade documentation for your installation method (Omnibus, source, or Docker)
  3. 3. Plan maintenance window as upgrades may require downtime
  4. 4. For Omnibus installations: run 'gitlab-ctl upgrade' or download and install the appropriate package for your version
  5. 5. For source installations: follow the upgrade guide to install the specific patched version
  6. 6. Verify the upgrade was successful by checking GitLab version after restart
  7. 7. Confirm the fix is applied by testing that developer-role users can no longer modify hidden merge requests they shouldn't have access to
Caveat Major version upgrades (e.g., 17.x to 18.x) may have breaking changes; review GitLab release notes for upgrade path considerations

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in GitLab Scoped from the published advisory
  • Consultation3.0 h
  • Implementation6.0 h
  • Testing4.0 h
  • Review / QA2.0 h
15.0 hours of engineering $2,640
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $4,224.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-6269 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2026-6269 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data