# GitLab GitLab Patch Release: 19.0.2, 18.11.5, 18.10.8

- Product: GitLab (https://whatsnew.fyi/product/gitlab)
- Vendor: GitLab
- Date: 2026-06-10
- Original notes: https://docs.gitlab.com/releases/patches/patch-release-gitlab-19-0-2-released/
- Permalink: https://whatsnew.fyi/product/gitlab/releases/2026-06-10-gitlab-patch-release-19.0.2-18.11.5-18.10.8

What's New is an index, not a publisher: every entry below links to the vendor's own release notes, which are the authoritative source. Entries are labelled where they are hand-curated sample data, pre-releases, or drawn from a secondary source such as a developer blog.

Reuse: the summaries, labels and curation here are © What's New. Quote freely with attribution and a link back; wholesale republication of the corpus is not permitted — terms: https://whatsnew.fyi/terms. The vendors' own release notes remain their publishers'.

---

On June 10, 2026, we released versions 19.0.2, 18.11.5, 18.10.8 for GitLab Community Edition (CE) and Enterprise Edition (EE). These versions contain important bug and security fixes, and we strongly…

- **security** — Fixed improper access control issue in Group SAML Identity API that could allow an authenticated user with group Owner role to take over another group member's GitLab account
- **security** — Fixed cross-site scripting issue in Analytics Dashboard that could allow an authenticated user with developer-role permissions to execute arbitrary client-side code
- **security** — Fixed denial of service issue in Grape API JSON parsing middleware that could allow an unauthenticated user to cause denial of service
- **security** — Fixed HTML injection issue in certain group setting fields that could allow an authenticated user to add unauthorized email addresses to a targeted user's account
- **security** — Fixed denial of service issue in Group Placeholder Reassignments API that could allow an authenticated user to cause denial of service through uncontrolled resource consumption
- **security** — Fixed improper access control issue in Merge Requests API
- **security** — Fixed server-side request forgery issue in Gitaly repository import
- **security** — Fixed HTML injection issue in CI/CD Catalog
- **security** — Fixed improper access control issue in Security Inventory
- **security** — Fixed authorization bypass issue in Merge Request diff
- **security** — Fixed improper access control issue in Todos API
- **security** — Fixed improper neutralization issue in Service Desk email template

Help us learn about your current experience with the documentation. Take the survey.
#### GitLab Patch Release: 19.0.2, 18.11.5, 18.10.8
On June 10, 2026, we released versions 19.0.2, 18.11.5, 18.10.8 for GitLab Community Edition (CE) and Enterprise Edition (EE).
These versions contain important bug and security fixes, and we strongly recommend that all self-managed GitLab installations be upgraded to one of these versions immediately. GitLab.com is already running the patched version. GitLab Dedicated customers do not need to take action.
GitLab releases fixes for vulnerabilities in patch releases. There are two types of patch releases: scheduled releases and ad-hoc critical patches for high-severity vulnerabilities. Scheduled releases are released twice a month on the second and fourth Wednesdays. For more information, please visit our releases handbook and security FAQ. You can see all of GitLab release blog posts here.
For security fixes, the issues detailing each vulnerability are made public on our issue tracker 30 days after the release in which they were patched.
We are committed to ensuring that all aspects of GitLab that are exposed to customers or that host customer data are held to the highest security standards. To maintain good security hygiene, it is highly recommended that all customers upgrade to the latest patch release for their supported version. You can read more best practices in securing your GitLab instance in our blog post.
###### Recommended action
We strongly recommend that all installations running a version affected by the issues described below are upgraded to the latest version as soon as possible.
When no specific deployment type (omnibus, source code, helm chart, etc.) of a product is mentioned, it means all types are affected.
##### Security fixes
###### Table of security fixes
TitleSeverity
Improper Access Control issue in Group SAML Identity API impacts GitLab EEHigh
Cross-site Scripting issue in Analytics Dashboard impacts GitLab EEHigh
Denial of Service issue in Grape API JSON parsing middleware impacts GitLab CE/EEHigh
HTML injection issue in certain group setting fields impacts GitLab EEHigh
Denial of Service issue in Group Placeholder Reassignments API impacts GitLab CE/EEMedium
Improper Access Control issue in Merge Requests API impacts GitLab CE/EEMedium
Server-Side Request Forgery issue in Gitaly repository import impacts GitLab CE/EEMedium
HTML injection issue in CI/CD Catalog impacts GitLab CE/EEMedium
Improper Access Control issue in Security Inventory impacts GitLab EEMedium
Authorization Bypass issue in Merge Request diff impacts GitLab CE/EELow
Improper Access Control issue in Todos API impacts GitLab CE/EELow
Improper Neutralization issue in Service Desk email template impacts GitLab CE/EELow
###### CVE-2026-6552 - Improper Access Control issue in Group SAML Identity API impacts GitLab EE
GitLab has remediated an issue 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.
Impacted Versions: GitLab EE: all versions from 15.5 before 18.10.8, 18.11 before 18.11.5, and 19.0 before 19.0.2CVSS 8.7 (CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:C/C:H/I:H/A:N)
Thanks cyberjoker for reporting this vulnerability through our HackerOne bug bounty program
###### CVE-2026-10087 - Cross-site Scripting issue in Analytics Dashboard impacts GitLab EE
GitLab has remediated an issue that under certain conditions could have allowed an authenticated user with developer-role permissions to execute arbitrary client-side code on behalf of a targeted user due to improper input sanitization in the Analytics Dashboard.
Impacted Versions: GitLab EE: all versions from 17.1 before 18.10.8, 18.11 before 18.11.5, and 19.0 before 19.0.2CVSS 8.7 (CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:C/C:H/I:H/A:N)
Thanks yvvdwf for reporting this vulnerability through our Hacker

_[Truncated at 4000 characters — full notes: https://docs.gitlab.com/releases/patches/patch-release-gitlab-19-0-2-released/]_