GitLab Patch Release: 18.3.2, 18.2.6, 18.1.6

Today, we are releasing versions 18.3.2, 18.2.6, 18.1.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, 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
Denial of Service issue in SAML Responses impacts GitLab CE/EE	High
Server-Side Request Forgery issue in Webhook custom header impacts GitLab CE/EE	High
Denial of Service issue in User-Controllable Fields impacts GitLab CE/EE	Medium
Denial of Service issue in endpoint file upload impacts GitLab CE/EE	Medium
Denial of Service issue in token listing operations impacts GitLab CE/EE	Medium
Information disclosure issue in runner endpoints impacts GitLab CE/EE	Medium

CVE-2025-2256 - Denial of Service issue in SAML Responses impacts GitLab CE/EE

GitLab has remediated an issue that could have allowed unauthorized users to render the GitLab instance unresponsive to legitimate users by sending multiple concurrent large SAML responses.

Impacted Versions: GitLab CE/EE: all versions from 7.12 before 18.1.6, 18.2 before 18.2.6, and 18.3 before 18.3.2
CVSS 7.5 (CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H)

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

CVE-2025-6454 - Server-Side Request Forgery issue in Webhook custom header impacts GitLab CE/EE

GitLab has remediated an issue that could have allowed authenticated users to make unintended internal requests through proxy environments by injecting crafted sequences.

Impacted Versions: GitLab CE/EE: all versions from 16.11 before 18.1.6, 18.2 before 18.2.6, and 18.3 before 18.3.2
CVSS 8.5 (CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:C/C:H/I:H/A:H)

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

CVE-2025-1250 - Denial of Service issue in User-Controllable Fields impacts GitLab CE/EE

GitLab has remediated an issue that could have allowed an authenticated user to stall background job processing by sending specially crafted commit messages, merge request descriptions, or notes.

Impacted Versions: GitLab CE/EE: all versions from 15.0 before 18.1.6, 18.2 before 18.2.6, and 18.3 before 18.3.2
CVSS: 6.5 (CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H)

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

CVE-2025-7337 - Denial of Service issue in endpoint file upload impacts GitLab CE/EE

GitLab has remediated an issue that could have allowed an authenticated user with Developer-level access to cause a persistent denial of service affecting all users on a GitLab instance by uploading large files.

Impacted Versions: GitLab CE/EE: all versions from 7.8 before 18.1.6, 18.2 before 18.2.6, and 18.3 before 18.3.2
CVSS: 6.5 (CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H)

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

CVE-2025-10094 - Denial of Service issue in token listing operations impacts GitLab CE/EE

GitLab has remediated an issue that could have allowed authenticated users to disrupt access to token listings and related administrative operations by creating tokens with excessively large names.

Impacted Versions: GitLab CE/EE: all versions from 10.7 before 18.1.6, 18.2 before 18.2.6, and 18.3 before 18.3.2
CVSS: 6.5 (CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H)

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

CVE-2025-6769 - Information disclosure issue in runner endpoints impacts GitLab CE/EE

GitLab has remediated an issue that could have allowed authenticated users to view administrator-only maintenance notes by accessing runner details through specific interfaces.

Impacted Versions: GitLab CE/EE: all versions from 15.1 before 18.1.6, 18.2 before 18.2.6, and 18.3 before 18.3.2
CVSS: 4.3 (CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:N/A:N)

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

Bug fixes

18.3.2

• Backport of 'Ignore silent_mode in clickhouse http calls'
• Backport of 'Update gitlab-shell to v14.45.0'
• Revert "Merge branch 'marina.mosti-543725-reviewer-dropdown-ce' into 'master'"
• Backport of "Only create ToC for headings with links"
• Backport of fix webauthn authentication in Firefox - 18.3
• Backport of move delayed deletion cronjob settings to CE
• Backport 'Disable gdk-update job in stable branch pipelines'
• Backport update to gitlab-sshd to relax allowed algorithms for FIPS
• Backport of 'Display MCP settings for root groups only'
• Backport of 'Fix shared group access for advanced code search'
• Backport: Fix nil error in Gitlab:Auth:IpRateLimiter
• Backport 'Add Compare link to submodule diffs' to 18.3
• Backport of "Revert 'New projects don't automatically inherit from group-level'"
• Backport of "Fix syncing remote stored Blobs with filenames with plus sign"
• Backport of 'Make FileLocationType.endLine nullable' for 18.3
• Backport of Update csp_enabled? to always return a boolean value
• Backport of Fix LdapAllAddOnSeatSyncWorker removing seats when no groups configured
• Backport 'Revert gem caching only in specific pipelines'
• Update gitlab-shell to v14.45.2 to allow ED25519 for FIPS
• [18.3] Remove flaky spec
• Backport of diff comment suggestions line range fix
• Adds checksum for ruby 3.2.9

18.2.6

• Update gitlab-shell to v14.45.0
• Backport of "Only create ToC for headings with links"
• Backport update to gitlab-sshd to relax allowed algorithms for FIPS
• Backport 'Disable gdk-update job in stable branch pipelines'
• Backport of 'Fix shared group access for advanced code search'
• Backport of 'Fix Bitbucket Server Importer enqueued job count'
• Backport of 'Fix: Geo::ModelMapper flakiness'
• Backport 'Add Compare link to submodule diffs' to 18.2
• Backport of 'Make FileLocationType.endLine nullable' for 18.2
• Backport of Update csp_enabled? to always return a boolean value
• Backport of "Fix syncing remote stored Blobs with filenames with plus sign"
• Update gitlab-shell to v14.45.2 to allow ED25519 for FIPS
• [18.2] Remove flaky spec
• Backport 18-2: Fix spec tag name source

18.1.6

• Backport of 'Fix cannot load such file – gitlab'
• Backport of Fix 'Bitbucket Server Importer enqueued job count'
• Backport of 'Make FileLocationType.endLine nullable' for 18.1

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.