patch-release-gitlab-17-11-2-released
GitLab Patch Release: 17.11.2, 17.10.6, 17.9.8
🔗 CVE IDs covered (3)
📋 Description
On May 7, 2025, we released versions 17.11.2, 17.10.6, 17.9.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, you can 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 all aspects of GitLab that are exposed to customers or that host customer data are held to
the highest security standards. As part of maintaining 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, this means all types are affected.
Security fixes
Table of security fixes
Title
Severity
Partial Bypass for Device OAuth flow using Cross Window Forgery
Medium
Denial of service by abusing Github import API
Medium
Group IP restriction bypass allows disclosing issue title of restricted project
Medium
Partial Bypass for Device OAuth flow using Cross Window Forgery
An issue has be…