GitLab Patch Release: 19.1.2, 19.0.4, 18.11.7

criticalCVE-2026-6896 CVE-2026-13320 CVE-2026-11827 CVE-2026-8472 CVE-2026-7492 CVE-2025-12506

On July 8, 2026, we released versions 19.1.2, 19.0.4, 18.11.7 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 Cross-site Scripting issue in vulnerability evidence table renderer impacts GitLab EE High HTML Injection in wiki markup rendering impacts GitLab CE/EE High Insufficiently Protected Credentials issue in repository mirroring impacts GitLab EE Medium Improper Access Control issue in work items impac

CSIRTS triage

vendor: GitLab product: GitLab Community Edition and Enterprise EditionOtheraffected: 19.1.2, 19.0.4, 18.11.7

What: These versions contain important bug and security fixes.
Who is affected: All self-managed GitLab installations are affected.
Urgency: Remediation is critical as it addresses multiple vulnerabilities.
Action: Upgrade to GitLab versions 19.1.2, 19.0.4, or 18.11.7.

AI-assisted analysis generated from the source advisory — verify against the original.

⚡ Watch GitLab Community Edition and Enterprise Edition

Get an email when a new GitLab Community Edition and Enterprise Edition advisory drops — max one per day, one-click unsubscribe.

Details

Source: GitLab Security Releases (INTL · vendor-psirt · site)
Severity: critical
Published: 2026-07-08
Exploitation: Not in CISA KEV at last sync

Original advisory: https://docs.gitlab.com/ja-jp/releases/patches/patch-release-gitlab-19-1-2-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-68960.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-133200.33% 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-118270.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-84720.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-74920.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-2025-125060.19% 30-day exploitation probability — currently an unlikely target, but scores change as exploit code circulates. Riskier than 9% of all scored CVEs.
Low exploitation riskCVE-2026-131510.17% 30-day exploitation probability — currently an unlikely target, but scores change as exploit code circulates. Riskier than 7% of all scored CVEs.
Low exploitation riskCVE-2026-63520.26% 30-day exploitation probability — currently an unlikely target, but scores change as exploit code circulates. Riskier than 18% of all scored CVEs.

Referenced CVEs

CVE	CSIRTS overview	External
CVE-2026-6896	coverage & exploitation status	NVD · CVE.org
CVE-2026-13320	coverage & exploitation status	NVD · CVE.org
CVE-2026-11827	coverage & exploitation status	NVD · CVE.org
CVE-2026-8472	coverage & exploitation status	NVD · CVE.org
CVE-2026-7492	coverage & exploitation status	NVD · CVE.org
CVE-2025-12506	coverage & exploitation status	NVD · CVE.org
CVE-2026-13151	coverage & exploitation status	NVD · CVE.org
CVE-2026-6352	coverage & exploitation status	NVD · CVE.org

Same CVEs, other sources

How other CERTs, PSIRTs and databases cover the vulnerabilities in this advisory.

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.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
unknownGitLab patch release notesgitlab · 2026-07-01
unknownGitLab Patch Release: 18.8.11gitlab · 2026-07-01
unknownGitLab Patch Release: 18.8.11gitlab · 2026-07-01