GitLab · published 2026-06-11
CVE-2026-6552
Routine No exploitation evidence; no EPSS score yet.
CVE-2026-6552 is not known to be exploited in the wild. Fixed upstream in GitLab 19.0.2, 18.11.5, 18.10.8. Routine: patch when convenient.
Jump to: Remediation Exploit intelDescription
Remediation#
Fixed upstream in GitLab 19.0.2, 18.11.5, 18.10.8.
Patch events
DevOpsGitLab
GitLab security releases: 19.0.2, 18.11.5, 18.10.8
Upgrade to
19.0.218.11.518.10.8Why: Vendor security release for server software (most severe: CVE-2026-10087).
Exploit intelligence#
| Signal | Value | Source |
|---|---|---|
| Known exploited | No | CISA KEV |
| Ransomware use | — | CISA KEV |
| EPSS (30-day exploitation probability) | — | FIRST EPSS |
| CVSS base score | — | CNA / CISA ADP |
| SSVC exploitation | — | CISA Vulnrichment |
| SSVC automatable | — | CISA Vulnrichment |
| SSVC technical impact | — | CISA Vulnrichment |
Description (from the CVE record)#
Rejected: This CVE ID has been rejected. GitLab determined that the reported behavior does not constitute a vulnerability: linking a group SAML identity requires the user to explicitly consent to that group controlling their GitLab account for sign-in, and management of group SAML identities by a group Owner is therefore expected behavior rather than an authorization bypass. No GitLab version was affected.
Quoted from the CVE Program record.