CVE-2026-15975
On July 29, 2026, we released versions 19.2.1, 19.1.3, 19.0.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 90 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 Sensitive Information Exposure issue in Workhorse impacts GitLab CE/EE High Mass Assignment issue in Pipeline Schedule API impacts GitLab CE/EE High Denial of Service issue in Merge Request Discussions impacts GitLab CE/EE High Race Condition issue in merge request approval rules impacts GitLab EE
CSIRTS triage
- What
- Multiple vulnerabilities have been discovered in GitLab.
- Who is affected
- Users of GitLab are affected.
- Urgency
- Remediation is not urgent as there are no known exploits for these vulnerabilities.
- Action
- Stay updated with GitLab releases and apply patches as they become available.
AI-assisted analysis generated from the source advisory — verify against the original.
⚡ Watch CVE-2026-15975
Get an email if CVE-2026-15975 is added to CISA KEV, gains public exploit code, or a new advisory cites it — max one per day, one-click unsubscribe.
Exploitation outlook
- Low exploitation risk0.39% 30-day exploitation probability — currently an unlikely target, but scores change as exploit code circulates. Riskier than 32% of all EPSS-scored CVEs.
Advisory coverage (7)
- high[NEW] [high] GitLab: Multiple vulnerabilitiescert-bund · 2026-07-30
- unknownNCSC-2026-0270 [1.00] [M/M] Vulnerabilities fixed in GitLab by GitLab Inc.ncsc-nl · 2026-07-30
- unknownGitLab Multiple Vulnerabilitieshkcert · 2026-07-30
- unknownMultiple Vulnerabilities in GitLab (July 30, 2026)cert-fr-avis · 2026-07-30
- highCVE-2026-15975: GitLab has remediated an issue in GitLab CE/EE affecting all versions from 11.8 before 19.0.5,…nvd · 2026-07-29
- criticalGitLab Patch Release: 19.2.1, 19.1.3, 19.0.5gitlab · 2026-07-29
- criticalGitLab Patch Release: 19.2.1, 19.1.3, 19.0.5gitlab · 2026-07-29
External references
Embed the live status
— this badge updates automatically when the KEV or exploit status changes. How to embed it →
[](https://www.csirts.com/cve/CVE-2026-15975)