GitLab Patch Release: 17.10.4, 17.9.6, 17.8.7

Today we are releasing versions 17.10.4, 17.9.6, 17.8.7 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
Denial of service via CI pipelines	Medium
Unintentionally authorizing sensitive actions on users behalf	Medium
IP Restriction Bypass through GraphQL Subscription	Medium
Unauthorized users can list the number of confidential issues	Medium
Debugging Information Disclosed	Low

Denial of service via CI pipelines

A Denial of Service (DoS) issue has been discovered in GitLab CE/EE affecting all up to 17.8.7, 17.9 prior to 17.9.6 and 17.10 prior to 17.10.4. A denial of service could occur upon injecting oversized payloads into CI pipeline exports. 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-2025-1677.

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

Unintentionally authorizing sensitive actions on users behalf

An issue has been discovered in GitLab CE/EE affecting all versions from 7.7 before 17.8.7, 17.9 before 17.9.6, and 17.10 before 17.10.4. Under certain conditions, an attacker could potentially trick users into unintentionally authorizing sensitive actions on their behalf. This is a medium severity issue (CVSS:3.1/AV:N/AC:H/PR:L/UI:R/S:U/C:H/I:H/A:N, 6.4). It is now mitigated in the latest release and is assigned CVE-2025-0362.

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

IP Restriction Bypass through GraphQL Subscription

An issue has been discovered in GitLab CE/EE affecting all versions from 13.12 before 17.8.7, 17.9 before 17.9.6, and 17.10 before 17.10.4. Under certain conditions users could bypass IP access restrictions and view 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-2408.

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

Unauthorized users can list the number of confidential issues

An issue has been discovered in GitLab EE affecting all versions from 17.1 before 17.8.7, 17.9 before 17.9.6, and 17.10 before 17.10.4, This allows attackers to perform targeted searches with sensitive keywords to get the count of issues containing the searched term. This is a medium severity issue (CVSS:3.0/AV:N/AC:H/PR:L/UI:N/S:U/C:H/I:N/A:N, 5.3). It is now mitigated in the latest release and is assigned CVE-2024-11129

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

Debugging Information Disclosed

An issue has been discovered in GitLab CE/EE affecting all versions from 17.9 before 17.9.6, and 17.10 before 17.10.4. The runtime profiling data of a specific service was accessible to unauthenticated users. This is a low severity issue (CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:L/I:N/A:N, 3.7). It is now mitigated in the latest release and is assigned CVE-2025-2469.

Thanks ap-wtioit for reporting this vulnerability through our HackerOne bug bounty program.

Bug fixes

17.10.4

• Cherry-picks multiple fixes into 17.10
• Fix invalid pipelines for scan execution policies
• Move group.cluster_agents field to CE
• Fixes merge requests updating URL with reports project
• Update approval rules name validation to include approval policy
• Workhorse golang-jwt/jwt upgrade to 5.2.2
• Golang Oauth2 upgrade to 0.27.0

17.9.6

• Workhorse golang-jwt/jwt upgrade to 5.2.2

17.8.7

• CI: Use gcr mirror in DinD (17.8 Backport)
• No-op ci_runner_machines_687967fa8a batched migrations - 17.8 backport
• Cherry-picks bug fixes into 17.8
• Backport fix in libarchive for CI
• CI: Use gcr mirror for DinD (17.8 Backport)
• [17.8 Backport] Check packages does not have .dind job in scope
• CI: Optionally enable dependency proxy (Backport 17.8)
• Workhorse golang-jwt/jwt upgrade to 5.2.2

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.