GitLab Patch Release: 19.2.1, 19.1.3, 19.0.5
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
- Important bug and security fixes have been released.
- Who is affected
- Self-managed GitLab installations are affected.
- Urgency
- Immediate upgrade is recommended due to critical severity of vulnerabilities.
- Action
- Upgrade to versions 19.2.1, 19.1.3, or 19.0.5.
AI-assisted analysis generated from the source advisory — verify against the original.
⚡ Watch GitLab
Get an email when a new GitLab advisory drops — max one per day, one-click unsubscribe.
Details
Original advisory: https://docs.gitlab.com/ja-jp/releases/patches/patch-release-gitlab-19-2-1-released/
Exploitation outlook
EPSS (FIRST.org) estimates each CVE’s probability of exploitation in the next 30 days — here is the CSIRTS.com read on those numbers.
- Low exploitation riskCVE-2026-62670.34% 30-day exploitation probability — currently an unlikely target, but scores change as exploit code circulates. Riskier than 26% of all scored CVEs.
- Low exploitation riskCVE-2026-124360.30% 30-day exploitation probability — currently an unlikely target, but scores change as exploit code circulates. Riskier than 23% of all scored CVEs.
- Low exploitation riskCVE-2026-159750.39% 30-day exploitation probability — currently an unlikely target, but scores change as exploit code circulates. Riskier than 32% of all scored CVEs.
- Low exploitation riskCVE-2026-131130.21% 30-day exploitation probability — currently an unlikely target, but scores change as exploit code circulates. Riskier than 11% of all scored CVEs.
- Low exploitation riskCVE-2026-165530.25% 30-day exploitation probability — currently an unlikely target, but scores change as exploit code circulates. Riskier than 17% of all scored CVEs.
- Low exploitation riskCVE-2026-63360.26% 30-day exploitation probability — currently an unlikely target, but scores change as exploit code circulates. Riskier than 17% of all scored CVEs.
- Low exploitation riskCVE-2026-143410.33% 30-day exploitation probability — currently an unlikely target, but scores change as exploit code circulates. Riskier than 25% of all scored CVEs.
- Low exploitation riskCVE-2026-30930.24% 30-day exploitation probability — currently an unlikely target, but scores change as exploit code circulates. Riskier than 15% of all scored CVEs.
- Low exploitation riskCVE-2026-150770.24% 30-day exploitation probability — currently an unlikely target, but scores change as exploit code circulates. Riskier than 16% of all scored CVEs.
- Low exploitation riskCVE-2026-158310.24% 30-day exploitation probability — currently an unlikely target, but scores change as exploit code circulates. Riskier than 15% of all scored CVEs.
Referenced CVEs
| CVE | CSIRTS overview | External |
|---|---|---|
| CVE-2026-6267 | coverage & exploitation status | NVD · CVE.org |
| CVE-2026-12436 | coverage & exploitation status | NVD · CVE.org |
| CVE-2026-15975 | coverage & exploitation status | NVD · CVE.org |
| CVE-2026-13113 | coverage & exploitation status | NVD · CVE.org |
| CVE-2026-16553 | coverage & exploitation status | NVD · CVE.org |
| CVE-2026-6336 | coverage & exploitation status | NVD · CVE.org |
| CVE-2026-14341 | coverage & exploitation status | NVD · CVE.org |
| CVE-2026-3093 | coverage & exploitation status | NVD · CVE.org |
| CVE-2026-15077 | coverage & exploitation status | NVD · CVE.org |
| CVE-2026-15831 | coverage & exploitation status | NVD · CVE.org |
| CVE-2026-14351 | coverage & exploitation status | NVD · CVE.org |
| CVE-2026-4672 | coverage & exploitation status | NVD · CVE.org |
| CVE-2025-14562 | coverage & exploitation status | NVD · CVE.org |
Same CVEs, other sources
How other CERTs, PSIRTs and databases cover the vulnerabilities in this advisory.
- high[NEW] [high] GitLab: Multiple vulnerabilitiescert-bund
- unknownNCSC-2026-0270 [1.00] [M/M] Vulnerabilities fixed in GitLab by GitLab Inc.ncsc-nl
- unknownGitLab Multiple Vulnerabilitieshkcert
- unknownMultiple Vulnerabilities in GitLab (July 30, 2026)cert-fr-avis
- mediumCVE-2026-6336: GitLab has remediated an issue in GitLab CE/EE affecting all versions from 16.6 before 19.0.5, …nvd
- highCVE-2026-6267: GitLab has remediated an issue in GitLab CE/EE affecting all versions from 10.1.0 before 19.0.5…nvd
- mediumCVE-2026-4672: GitLab has remediated an issue in GitLab CE/EE affecting all versions from 18.4 before 19.0.5, …nvd
- mediumCVE-2026-3093: GitLab has remediated an issue in GitLab CE/EE affecting all versions from 14.0 before 19.0.5, …nvd
- mediumCVE-2026-16553: GitLab has remediated an issue in GitLab EE affecting all versions from 18.8 before 19.0.5, 19…nvd
- highCVE-2026-15975: GitLab has remediated an issue in GitLab CE/EE affecting all versions from 11.8 before 19.0.5,…nvd
- mediumCVE-2026-15831: GitLab has remediated an issue in GitLab EE affecting all versions from 19.1 before 19.1.3 and…nvd
- mediumCVE-2026-15077: GitLab has remediated an issue in GitLab EE affecting all versions from 19.1 before 19.1.3 and…nvd
Recent advisories for GitLab Patch Release
A cluster of recent advisories against the same product widens the attack surface — attackers routinely chain freshly published CVEs on one product, so review these together.
- criticalGitLab Patch Release: 19.2.1, 19.1.3, 19.0.5gitlab · 2026-07-29
- criticalGitLab Patch Release: 19.1.2, 19.0.4, 18.11.7gitlab · 2026-07-08
- criticalGitLab Patch Release: 19.1.2, 19.0.4, 18.11.7gitlab · 2026-07-08
- unknownGitLab Patch Release: 18.8.11gitlab · 2026-07-01
- unknownGitLab patch release notesgitlab · 2026-07-01
- unknownGitLab Patch Release: 18.8.11gitlab · 2026-07-01
More from GitLab Security Releases
- criticalGitLab Patch Release: 19.2.1, 19.1.3, 19.0.52026-07-29
- criticalGitLab Patch Release: 19.1.2, 19.0.4, 18.11.72026-07-08
- criticalGitLab Patch Release: 19.1.2, 19.0.4, 18.11.72026-07-08
- unknownGitLab patch release notes2026-07-01
- unknownGitLab Patch Release: 18.8.112026-07-01