CVE-2026-12053
On June 24, 2026, we released versions 19.1.1, 19.0.3, 18.11.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 Cross-site Scripting issue in Analytics Dashboard impacts GitLab EE High Cross-site Scripting issue in Web IDE workbench asset handler impacts GitLab CE/EE High Information Disclosure issue in Duo Workflows impacts GitLab EE High Authorization Bypass issue in Virtual Registry Cleanup Policy API i
CSIRTS triage
- What
- Multiple vulnerabilities have been discovered in GitLab.
- Who is affected
- Users of GitLab products.
- Urgency
- Remediation is necessary, but the severity is currently unknown.
- Action
- Users should monitor for updates and advisories.
AI-assisted analysis generated from the source advisory — verify against the original.
⚡ Watch CVE-2026-12053
Get an email if CVE-2026-12053 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.33% 30-day exploitation probability — currently an unlikely target, but scores change as exploit code circulates. Riskier than 25% of all EPSS-scored CVEs.
Advisory coverage (4)
- unknownNCSC-2026-0211 [1.00] [M/H] Vulnerabilities fixed in GitLab Community Edition and Enterprise Editionncsc-nl · 2026-06-25
- unknownGitLab Multiple Vulnerabilitieshkcert · 2026-06-25
- unknownMultiple vulnerabilities in GitLab (June 25, 2026)cert-fr-avis · 2026-06-25
- criticalGitLab Patch Release: 19.1.1, 19.0.3, 18.11.6gitlab · 2026-06-24
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-12053)