Today we are releasing versions 17.9.1, 17.8.4, 17.7.6 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
XSS in k8s proxy endpoint
An issue has been discovered in GitLab CE/EE affecting all versions from 15.10 prior to 17.7.6, 17.8 prior to 17.8.4, and 17.9 prior to 17.9.1. A proxy feature could potentially allow unintended content rendering leading to XSS under specific circumstances.
This is a high severity issue (CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:C/C:H/I:H/A:N
, 8.7).
It is now mitigated in the latest release and is assigned CVE-2025-0475.
Thanks joaxcar for reporting this vulnerability through our HackerOne bug bounty program.
XSS Maven Dependency Proxy
A Cross Site Scripting (XSS) vulnerability in GitLab-EE affecting all versions from 16.6 prior to 17.7.6, 17.8 prior to 17.8.4, and 17.9 prior to 17.9.1 allows an attacker to bypass security controls and execute arbitrary scripts in a user's browser under specific conditions.
This is a high severity issue (CVSS:3.1/AV:N/AC:H/PR:L/UI:R/S:C/C:H/I:H/A:N
, 7.7).
It is now mitigated in the latest release and is assigned CVE-2025-0555.
Thanks joaxcar for reporting this vulnerability through our HackerOne bug bounty program.
HTML injection leads to XSS on self hosted instances
An issue has been discovered in GitLab CE/EE affecting all versions from 16.6 before 17.7.6, 17.8 before 17.8.4, and 17.9 before 17.9.1. An attacker could inject HMTL into the child item search potentially leading to XSS in certain situations.
This is a medium severity issue (CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:C/C:L/I:L/A:N
, 5.4).
It is now mitigated in the latest release and is assigned CVE-2024-8186.
Thanks joaxcar for reporting this vulnerability through our HackerOne bug bounty program.
Improper Authorisation Check Allows Guest User to Read Security Policy
A vulnerability in GitLab-EE affecting all versions from 16.2 prior to 17.7.6, 17.8 prior to 17.8.4, and 17.9 prior to 17.9.1 allows a Guest user to read Security policy YAML.
This is a medium severity issue (CVSS:3.1/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-10925.
Thanks yuki_osaki for reporting this vulnerability through our HackerOne bug bounty program.
Planner role can read code review analytics in private projects
Improper authorization in GitLab EE affecting all versions from 17.7 prior to 17.7.6, 17.8 prior to 17.8.4, 17.9 prior to 17.9.1 allow users with limited permissions to access potentially sensitive project analytics data.
This is a medium severity issue (CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:N/A:N
, 4.3).
It is now mitigated in the latest release and is assigned CVE-2025-0307.
Thanks weasterhacker for reporting this vulnerability through our HackerOne bug bounty program.
Bug fixes
17.9.1
- Backport - Merge branch 'revert-e78b1a9f' into 'master'
- Backport/fix ambiguous pipeline 17 9
- Make it possible for ignore unexpected EOFs in SSL connections
- Allow Duo Chat to be resizable on self-managed (backport)
- Merge branch 'mdc/include-build-assets-image-job-sync-pipelines' into 'master'
- Fix instance level dashboard by default severity override
17.8.4
- Bump gitlab-exporter to v15.2.0
- [Backport] Return false for pending_migrations? if indexing disabled
- Merge branch '10443-fix-workhorse-verify' into 'master'
- Revert stricter workhorse route regexes
- Use primary DB when authenticating via job token in jobs API
- Backport/fix ambiguous pipeline 17 8
- Backport add more custom exit codes for CI/CD failures MRs and fix assets caching in scheduled cache-assets:production job
- Backport fix CH version incompatibility
- Merge branch 'mdc/include-build-assets-image-job-sync-pipelines' into 'master'
- Make it possible for ignore unexpected EOFs in SSL connections
- Update dependency gitlab-exporter to v15.2.0
- [Backport] Return false for pending_migrations? if indexing disabled
- Merge branch '10443-fix-workhorse-verify' into 'master'
- Revert stricter workhorse route regexes
- Use primary DB when authenticating via job token in jobs API
17.7.6
- Merge branch '10443-fix-workhorse-verify' into 'master'
- Revert stricter workhorse route regexes
- Fix failed jobs widget polling issue
- Backport fix for ambiguous created_at
- Backport add more custom exit codes for CI/CD failures MRs and fix assets caching in scheduled cache-assets:production job
- Merge branch 'mdc/include-build-assets-image-job-sync-pipelines' into 'master'
- Make it possible for ignore unexpected EOFs in SSL connections
- Merge branch '10443-fix-workhorse-verify' into 'master'
- Revert stricter workhorse route regexes
Updating
To update GitLab, see the update page. To update Gitlab Runner, see the Updating the Runner page.
Note: GitLab releases have skipped 17.7.5 and 17.8.3. There are no patches with these version numbers.
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.
We’re combining patch and security releases
This improvement in our release process matches the industry standard and will help GitLab users get information about security and bug fixes sooner, read the blog post here.
We want to hear from you
Enjoyed reading this blog post or have questions or feedback? Share your thoughts by creating a new topic in the GitLab community forum.
Share your feedback