CVE-2026-6552: Authorization Bypass Through User-Controlled Key in GitLab
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.
Metrics
- CVSS v3.1
- 8.7
- Severity
- HIGH
- Fixed in
- 18.10.8
- Affected Products
- 1
HarborGuard Analysis
Synopsis
An authorization bypass vulnerability in GitLab EE's Group SAML identity management allows an authenticated attacker to take over another group member's account. The vulnerability is reachable over the network and requires no victim interaction, but the attacker must hold a group Owner role within the targeted GitLab group. Successful exploitation gives the attacker full control of the victim's GitLab account, enabling broad access to repositories, pipelines, and organization data. Patched-image rebuilds at versions 18.10.8, 18.11.5, and 19.0.2 are available on HarborGuard for affected environments.
HarborGuard Coverage
Detection of CVE-2026-6552 is available across every HarborGuard environment, with the CVE matched against customer images within minutes of ingestion from upstream advisory feeds, including custom-built GitLab EE images. Coverage extends to images scanned in both registry and CI/CD pipeline contexts.
AvailableHarborGuard is capable of scoring this CVE at CVSS 8.7 (HIGH) and weighting it against each environment's compliance policy to determine priority. Triage routing routes findings to the appropriate team inbox within each customer organization based on configured ownership rules.
AvailableA patched-image rebuild targeting versions 18.10.8, 18.11.5, and 19.0.2 is available on HarborGuard for any environment running an affected GitLab EE version. For customers who opt into auto-remediation, HarborGuard performs the rebuild, runs a regression test suite, and opens a PR against affected workloads automatically.
AvailableExploit Conditions
- Network reachabilityRequired
The attacker must reach the GitLab instance over the network; there is no requirement for local or physical access.
- AuthenticationRequired
The attacker must hold a group Owner role within the targeted GitLab group; any lower-privilege account is not sufficient.
- Victim interactionNot required
No action is required from the victim account holder for exploitation to succeed.
- Attack complexityDetail
The exploit is reliable and imposes no special race conditions or environmental dependencies once the attacker has the required group Owner privilege.
Blast Radius
- The attacker gains full control of the victim's GitLab account, including the ability to read and exfiltrate all repositories and sensitive project data accessible to that account.
- The attacker can push malicious code, modify CI/CD pipeline configurations, or inject supply-chain artifacts under the victim's identity.
- The attacker can leverage the compromised account to escalate further within the organization, inviting collaborators, modifying group settings, or accessing secrets stored in GitLab CI variables.
How HarborGuard Handles This
Available on HarborGuard: detection for CVE-2026-6552 activates as soon as the advisory is ingested, matching against any customer image built on a vulnerable GitLab EE release (15.5 through the fix boundaries). For customers who opt into auto-remediation, HarborGuard can rebuild the affected image at a patched version (18.10.8, 18.11.5, or 19.0.2 depending on the release branch in use), run a regression test pass, and open a PR against affected workloads; the median time from CVE publication to merged patch PR for high-severity issues is around 90 minutes in environments with auto-remediation enabled. Where compliance policy requires manual approval, the rebuilt image and full CVSS detail are surfaced in the dashboard for engineer review. Because the vulnerability requires group Owner-level access, short-term compensating controls include auditing group Owner assignments and restricting SAML identity-linking permissions via GitLab's group settings until the patched image is deployed.
Fix available
- GitLab / GitLab< 18.10.8 (from 15.5) · < 18.11.5 (from 18.11) · < 19.0.2 (from 19.0)
CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:C/C:H/I:H/A:N