# CVE-2026-6552: This CVE ID has been rejected.


- **Severity:** Not scored
- **Exploited in the wild:** Not known
- **Fix available:** Yes
- **Published:** 11 Jun 2026
- **Updated:** 31 Jul 2026
- **Also known as:** BIT-gitlab-2026-6552, GHSA-r82j-g6q9-mvx8, MINI-2gw6-6h97-3q8g, MINI-35j5-wgcp-288r, MINI-3jxj-5q3f-r9x8, MINI-47hp-g9hx-jccw, MINI-4j97-765h-jw8j, MINI-4mwp-hmm5-wp5m, MINI-4phv-7c59-5wpj, MINI-5cvj-48vg-mcpf, MINI-67x6-65vv-hqw7, MINI-6978-4jhg-gr53, MINI-6gfq-mwp6-xq27, MINI-74qr-pq7r-2wqj, MINI-7p77-g3xx-q6vp, MINI-9449-w36c-6j9g, MINI-c8x8-8pqh-cg5m, MINI-f7f9-wj7g-rmf9, MINI-fhxf-x7p8-fh82, MINI-fx3h-4wq4-qvh3, MINI-g442-mjvm-9mrq, MINI-gc3r-cwm7-694v, MINI-gcq9-wq95-rq3w, MINI-gwpv-x9ch-2673, MINI-hg6v-f6mp-rp62, MINI-hjxw-3w37-crj8, MINI-j834-83g8-qcpx, MINI-jc8f-9mxj-xjcg, MINI-jmq7-qf8w-xmcw, MINI-jxwc-hq8v-g7x6, MINI-mr2x-r9hp-3c78, MINI-pcm7-cmx8-mj94, MINI-pcvg-7wfw-xwgm, MINI-prq3-9j7m-pq87, MINI-px94-72rp-86r7, MINI-qhr6-h32g-w6j9, MINI-qj5r-w32c-5c4f, MINI-r5g7-frfq-4jpq, MINI-r9pc-j2g9-c58v, MINI-rr9m-j49j-hp4v, MINI-v323-g5r5-p3v6, MINI-vv2j-p5gp-xhw3, MINI-w676-x46g-mpf4, MINI-wcgw-r388-x693, MINI-x9gp-394p-hv85, MINI-xgv5-555p-mmc6, UBUNTU-CVE-2026-6552

## What is CVE-2026-6552?

CVE-2026-6552 is a vulnerability in gitlab, published on 11 Jun 2026. 

### Official description

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.

## Which versions are affected by CVE-2026-6552?

1 open source package ship an affected version, including gitlab.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `gitlab` | Bitnami | From 15.5.0 | 18.10.8, 18.11.5, 19.0.2 |

## How do I fix CVE-2026-6552?

Upgrade gitlab to a fixed version for your release line: 18.10.8, 18.11.5 or 19.0.2.

## Is CVE-2026-6552 being exploited?

There is no known exploitation of CVE-2026-6552 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-6552 and fix it if it is affected.

What it is: CVE-2026-6552 is a vulnerability in gitlab, published on 11 Jun 2026. 
Exploitation: There is no known exploitation of CVE-2026-6552 in the wild and no public exploit code.

Affected packages and fixed versions:
- gitlab (Bitnami): affected from 15.5.0; fixed in 18.10.8, 18.11.5, 19.0.2

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-6552/ (Markdown: https://insights.sbomify.com/CVE-2026-6552/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-6552
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-6552
- OSV: https://osv.dev/vulnerability/CVE-2026-6552

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-6552/
Summaries are generated and may contain mistakes; the official description above is the record.