GitLab Patch Release: 18.5.1, 18.4.3, 18.3.5

Today, we are releasing versions 18.5.1, 18.4.3, 18.3.5 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

Title	Severity
Improper access control issue in runner API impacts GitLab EE	High
Denial of service issue in event collection impacts GitLab CE/EE	High
Denial of service issue in JSON validation impacts GitLab CE/EE	High
Denial of service issue in upload impacts GitLab CE/EE	Medium
Incorrect Authorization issue in pipeline builds impacts GitLab CE	Medium
Business logic error issue in group memberships impacts GitLab EE	Low
Missing authorization issue in quick actions impacts GitLab EE	Low

CVE-2025-11702 - Improper access control issue in runner API impacts GitLab EE

GitLab has remediated an issue that could have allowed an authenticated user with specific permissions to hijack project runners from other projects.

Impacted Versions: GitLab EE: all versions from 17.1 before 18.3.5, 18.4 before 18.4.3, and 18.5 before 18.5.1
CVSS 8.5 (CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:C/C:H/I:H/A:H)

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

CVE-2025-10497 - Denial of service issue in event collection impacts GitLab CE/EE

GitLab has remediated an issue that could have allowed an unauthenticated user to cause a denial of service condition by sending specially crafted payloads.

Impacted Versions: GitLab CE/EE: all versions from 17.10 before 18.3.5, 18.4 before 18.4.3, and 18.5 before 18.5.1
CVSS 7.5 (CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H)

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

CVE-2025-11447 - Denial of service issue in JSON validation impacts GitLab CE/EE

GitLab has remediated an issue that could have allowed an unauthenticated user to cause a denial of service condition by sending GraphQL requests with crafted JSON payloads.

Impacted Versions: GitLab CE/EE: all versions from 11.0 before 18.3.5, 18.4 before 18.4.3, and 18.5 before 18.5.1
CVSS 7.5 (CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H)

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

CVE-2025-11974 - Denial of service issue in upload impacts GitLab CE/EE

GitLab has remediated an issue that could have allowed an unauthenticated user to create a denial of service condition by uploading large files to specific API endpoints.

Impacted Versions: GitLab CE/EE: all versions from 11.7 before 18.3.5, 18.4 before 18.4.3, and 18.5 before 18.5.1
CVSS 6.5 (CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H)

This vulnerability has been discovered internally by GitLab team member David Fernandez

CVE-2025-11971 - Incorrect Authorization issue in pipeline builds impacts GitLab CE

GitLab has remediated an issue that could have allowed an authenticated user to trigger unauthorized pipeline executions by manipulating commits.

Impacted Versions: GitLab EE: all versions from 10.6 before 18.3.5, 18.4 before 18.4.3, and 18.5 before 18.5.1
CVSS 6.5 (CVSS:3.1/AV:N/AC:H/PR:L/UI:R/S:C/C:H/I:L/A:N)

CVE-2025-6601 - Business logic error issue in group memberships impacts GitLab EE

GitLab has remediated an issue that under certain conditions could have allowed authenticated users to gain unauthorized project access by exploiting the access request approval workflow.

Impacted Versions: GitLab EE: all versions from 18.4 before 18.3.5, 18.4 before 18.4.3, and 18.5 before 18.5.1
CVSS 3.8 (CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:L/I:L/A:N)

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

CVE-2025-11989 - Missing authorization issue in quick actions impacts GitLab EE

GitLab has remediated an issue that could have allowed an authenticated user to execute unauthorized quick actions by including malicious commands in specific descriptions.

Impacted Versions: GitLab EE: all versions from 17.6 before 18.3.5, 18.4 before 18.4.3, and 18.5 before 18.5.1
CVSS 3.7 (CVSS:3.1/AV:N/AC:H/PR:L/UI:R/S:U/C:L/I:L/A:N)

This vulnerability has been discovered internally by GitLab team member Eva Kadlecová

Bug fixes

18.5.1

• [18.5] Downgrade redis-rb gem to v5.4.0
• [18.5] Fix connection pool errors when health check is running
• Backport: Test: dismiss duo popover
• Backport of 'Fix work item status fallback to use lifecycle-aware default'
• Support stable branch pipelines (18.5 backport)

18.4.3

• pgbouncer: Use new bitnamilegacy container registry (18.4 backport)
• [18.4] Revert discarded database pool check in load balancer
• Backport 'Fix group wiki inaccessible after deleting and creating group with the same name'
• Backport ElasticIndexBulkCronWorker throwing NoMethodError for epics
• [18.4] Fix Geo routes leaking to other specs
• Backport Allow Zoekt in Search API for blobs scope when Elasticsearch disabled
• Backport fix-agentic-chat-service-url-for-shm for 18.4 EE
• Backport Zoekt Kaminari raises an exception if total_count gets negative
• Backport (18.4) "Update dependency @gitlab/web-ide to ^0.0.1-dev-20250925110326"
• Backport branch 'sh-fix-login-issues-ubuntu-fips' into 'master'
• Backport "Improve performance of ready to merge GraphQL query"
• [18.4] Fix flaky callout dismissal specs
• Backport: Ensure consistent approval permissions between UI, API and graphql
• Backport of 'Show whitespace message when there's nothing to show'
• [18.4] Downgrade redis-rb gem to v5.4.0
• [18.4] Fix connection pool errors when health check is running
• Backport 'Remove available auto merge strategies from ready to merge query'
• 18.4 Backport of 'Fix query for finding existing Jira issues for vulnerabilities'
• Backport: Test: dismiss duo popover
• Support stable branch pipelines (18.4 backport)

18.3.5

• pgbouncer: Use new bitnamilegacy container registry (18.3 backport)
• [18.3] Prevent session creation for sessionless users
• Backport of 'Fix Start free trial link for self-managed instances'
• Backport 'Fix SlackIntegration duplicate bug when inheriting from parent' to 18.3
• Backport ElasticIndexBulkCronWorker throwing NoMethodError for epics
• Backport of 'Recreate SlackIntegration records on descendant integration on update'
• [18.3] Fix json validation for elasticsearch_aws_role_arn
• [18.3] Fix flaky callout dismissal specs
• [18.3] Fix Geo routes leaking to other specs
• Backport (18.3) "Update dependency @gitlab/web-ide to ^0.0.1-dev-20250925110326"
• Backport of 'Show whitespace message when there's nothing to show'
• [18.3] Downgrade redis-rb gem to v5.4.0
• Backport: Test: dismiss duo popover 18-3
• Support stable branch pipelines (18.3 backport)

Important notes on upgrading

These versions do not include any new migrations, and for multi-node deployments, should not require any downtime.

Please be aware that by default the Omnibus packages will stop, run migrations, and start again, no matter how “big” or “small” the upgrade is. This behavior can be changed by adding a /etc/gitlab/skip-auto-reconfigure file, which is only used for updates.

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.