- What: GitLab released versions 18.8.4, 18.7.4, and 18.6.6 for Community Edition (CE) and Enterprise Edition (EE).
- Impact: Self-managed GitLab installations should be upgraded to these versions to address important bug and security fixes.
To search repositories and projects, login to gitlab.com. Suggestions GitLab Duo Agent Platform Code Suggestions (AI) CI/CD GitLab on AWS GitLab on Google Cloud Why GitLab? â Back to releases Feb 10, 2026 - FĂ©lix Veillette-Potvin GitLab Patch Release: 18.8.4, 18.7.4, 18.6.6 Learn more about GitLab Patch Release: 18.8.4, 18.7.4, 18.6.6 for GitLab Community Edition (CE) and Enterprise Edition (EE). Today, we are releasing versions 18.8.4, 18.7.4, 18.6.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. 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 Incomplete Validation issue in Web IDE impacts GitLab CE/EE High Denial of Service issue in GraphQL introspection impacts GitLab CE/EE High Denial of Service issue in JSON validation middleware impacts GitLab CE/EE High Cross-site Scripting issue in Code Flow impacts GitLab CE/EE High HTML Injection issue in test case titles impacts GitLab CE/EE High Denial of Service issue in Markdown processor impacts GitLab CE/EE Medium Denial of Service issue in Markdown Preview impacts GitLab CE/EE Medium Denial of Service issue in dashboard impacts GitLab EE Medium Server-Side Request Forgery issue in Virtual Registry impacts GitLab EE Medium Improper Validation issue in diff parser impacts GitLab CE/EE Medium Server-Side Request Forgery issue in Git repository import impacts GitLab CE/EE Medium Authorization Bypass issue in iterations API impacts GitLab EE Medium Missing Authorization issue in GLQL API impacts GitLab CE/EE Low Stored HTML Injection issue in project label impacts GitLab CE/EE Low Authorization Bypass issue in Pipeline Schedules API impacts GitLab CE/EE Low CVE-2025-7659 - Incomplete Validation issue in Web IDE impacts GitLab CE/EE GitLab has remediated an issue that could have allowed an unauthenticated user to steal tokens and access private repositories by abusing incomplete validation in the Web IDE. Impacted Versions: GitLab CE/EE: all versions from 18.2 before 18.6.6, 18.7 before 18.7.4, and 18.8 before 18.8.4 CVSS 8.0 ( CVSS:3.1/AV:N/AC:H/PR:N/UI:R/S:C/C:H/I:H/A:N ) Thanks cav0ur for reporting this vulnerability through our HackerOne bug bounty program CVE-2025-8099 - Denial of Service issue in GraphQL introspection impacts GitLab CE/EE GitLab has remediated an issue that, under certain conditions, could have allowed an unauthenticated user to cause denial of service by sending repeated GraphQL queries. Impacted Versions: GitLab CE/EE: all versions from 10.8 before 18.6.6, 18.7 before 18.7.4, and 18.8 before 18.8.4 CVSS 7.5 ( CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H ) Thanks foxribeye for reporting this vulnerability through our HackerOne bug bounty program CVE-2026-0958 - Denial of Service issue in JSON validation middleware impacts GitLab CE/EE GitLab has remediated an issue that could have allowed an unauthenticated user to cause denial of service through memory or CPU exhaustion by bypassing JSON validation middleware limits. Impacted Versions: GitLab CE/EE: all versions from 18.4 before 18.6.6, 18.7 before 18.7.4, and 18.8 before 18.8.4 CVSS 7.5 ( CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H ) Thanks elbo7 for reporting this vulnerability through our HackerOne bug bounty program CVE-2025-14560 - Cross-site Scripting issue in Code Flow impacts GitLab CE/EE GitLab has remediated an issue that, under certain conditions could have allowed an authenticated user to perform unauthorized actions on behalf of another user by injecting content into vulnerabili