GitLab Patch Release: 17.11.2, 17.10.6, 17.9.8

Today we are releasing 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 been discovered in GitLab CE/EE affecting all versions starting from 17.3 prior to 17.9.8, from 17.10 prior to 17.10.6, and from 17.11 prior to 17.11.2. Under certain conditions Device OAuth flow protections could be bypassed, enabling authorization form submission through minimal user interaction. This is a medium severity issue (CVSS:3.1/AV:N/AC:H/PR:N/UI:R/S:U/C:H/I:H/A:N, 6.8). It is now mitigated in the latest release and is assigned CVE-2025-0549.

Thanks sim4n6 for reporting this vulnerability through our HackerOne bug bounty program.

Denial of service by abusing Github import API

An issue has been discovered in GitLab CE/EE affecting all versions starting from 17.1 prior to 17.9.8, from 17.10 prior to 17.10.6, and from 17.11 prior to 17.11.2. It was possible to cause a DoS condition via GitHub import requests using a malicious crafted payload. This is a medium severity issue (CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H, 6.5). It is now mitigated in the latest release and is assigned CVE-2024-8973.

Thanks a92847865 for reporting this vulnerability through our HackerOne bug bounty program.

Group IP restriction bypass allows disclosing issue title of restricted project

An issue has been discovered in GitLab CE/EE affecting all versions from 12.0 before 17.9.8, 17.10 before 17.10.6, and 17.11 before 17.11.2. Under certain conditions users could bypass IP access restrictions of a group, enabling them to disclose sensitive information. This is a medium severity issue (CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N, 5.3). It is now mitigated in the latest release and is assigned CVE-2025-1278.

Thanks iamgk808 for reporting this vulnerability through our HackerOne bug bounty program.

Bug fixes

17.11.2

• Merge branch 'renovate-e2e/gitlab-qa-15.x' into '17-11-stable-ee'
• [backport] Fix subgroup search redirect if SAML auth expired
• Fix MR diffs endpoint to respond with pagination headers
• Fix token prefix change when PAT prefix is nil
• [backport] Respect fork filter for global zoekt search
• [17.11] Bump graphql gem to 2.4.13
• [Backport] Allow SSO enforcer to skip root owner check
• [17.11] Only check records with encrypted data in gitlab:doctor:encryption_keys
• Change to async_delete for ci_running_builds.runner_id
• Merge branch 'pb-fix-matrix-use-case' into 'master'
• Update gitlab-development-kit digest to 59037d8
• Backport (17.11): Bump Devfile gem to 0.4.3
• Backport (17.11): Ensure all LFK's are processed regardless of duration
• [17.11 Backport] Change the travel date for analytics/dashboards_spec.rb
• config/git: Fix misdetected shell path (17.11 backport)

17.10.6

• [17.10] Bump graphql gem to 2.4.13
• [17.10] Only check records with encrypted data in gitlab:doctor:encryption_keys
• Change to async_delete for ci_running_builds.runner_id
• Update gitlab-development-kit digest to 59037d8
• Backport (17.10): Bump Devfile gem to 0.4.3
• Cherry pick '8995-json-parse-utf8' into '17-10-stable'

17.9.8

• [17.9] Bump graphql gem to 2.4.13
• [17.9] Only check records with encrypted data in gitlab:doctor:encryption_keys
• Update gitlab-development-kit digest to 59037d8
• Backport (17.9): Bump devfile gem to v0.4.3

Updating

To update GitLab, see the Update page. To update Gitlab Runner, see the Updating the Runner page.

Receive Patch Notifications

To receive patch blog notifications delivered to your inbox, visit our contact us page. To receive release notifications via RSS, subscribe to our patch release RSS feed or our RSS feed for all releases.