dbcve.org
GitLabApplication

CVE-2026-6552

HIGH · 8.7 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 →
93/100
Remediation priority · Urgent
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 EE affecting all versions from 15.5 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 group Owner role to take over another group member's GitLab account due to improper authorization in the Group SAML identity management functionality.

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

A group Owner with SAML identity management permissions could perform improper authorization checks in GitLab EE's Group SAML identity functionality, allowing takeover of another group member's GitLab account through identity manipulation.

MitigationUpgrade GitLab EE to version 18.10.8, 18.11.5, or 19.0.2 or later. Verify SAML group membership mappings and authorization controls post-upgrade.

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.5.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
High
User interaction
None
Scope
Changed
Confidentiality
High
Integrity
High
Availability
None

CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:C/C:H/I:H/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. Confirm GitLab EE edition
    Run `grep -E '^gitlab-ee|^gitlab-ee' /opt/gitlab/version-manifest.txt` or check the About page in the UI - this vulnerability only affects GitLab Enterprise Edition (EE), not Community Edition (CE)
    Affected if The installation is GitLab Enterprise Edition (EE)
  2. Identify installed GitLab version
    Run `gitlab-rake gitlab:env:info` or check the GitLab UI at /help (or /-/infO). Extract the version number (e.g., 18.10.0, 19.0.1)
    Affected if Version falls in ranges: >= 15.5.0 AND < 18.10.8, OR >= 18.11.0 AND < 18.11.5, OR >= 19.0.0 AND < 19.0.2
  3. Verify SAML SSO is configured for groups
    Navigate to Group Settings > SAML SSO (or check via API: `GET /groups/:id/saml_identities` with admin credentials). Look for configured SAML providers at the group level
    Affected if SAML identity providers are configured for any group in the GitLab instance
  4. Check for group Owner users with SAML identity permissions
    Review group membership roles. In UI: Group Settings > Members. Or query API: `GET /groups/:id/members`. Identify users with Owner role who have SAML identity management access
    Affected if Any group has an Owner user who can manage SAML identities for that group

User is affected if running GitLab EE version 18.10.7 or earlier, 18.11.4 or earlier, or 19.0.1 or earlier AND has SAML SSO configured for groups with Owner users who can manage SAML identities.

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 EE to version 18.10.8, 18.11.5, or 19.0.2 or later. Verify SAML group membership mappings and authorization controls post-upgrade.

Recommended fix High confidence

18.10.8, 18.11.5, or 19.0.2 (or later stable release)

  1. 1. Back up your GitLab instance database and repositories before proceeding with the upgrade.
  2. 2. Review GitLab's upgrade path documentation to ensure you follow the correct sequential upgrade path for your current version.
  3. 3. Plan for maintenance window as GitLab upgrade will require service downtime.
  4. 4. For installations on GitLab.com SaaS: Contact GitLab support to ensure the patch is applied.
  5. 5. For self-managed GitLab: Upgrade to version 18.10.8, 18.11.5, or 19.0.2 (or any subsequent stable release) following your preferred upgrade method (package upgrade, source upgrade, or Docker/container upgrade).
  6. 6. After upgrade, verify that the Group SAML identity functionality is working correctly and test that authorization controls are properly enforced.
Caveat Upgrading across multiple major versions (e.g., from 15.x to 18.x/19.x) may introduce breaking changes; review GitLab's release notes for each intermediate version for compatibility concerns.

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
  • Testing3.0 h
  • Review / QA2.0 h
14.0 hours of engineering $2,490
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-6552 — 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-6552 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