Unauthenticated RCE in GitLab CE/EE (widely used enterprise DevOps platform) with CVSS 10.0 — high-impact remote compromise of servers used across organizations.
CVE-2026-110264
Unauthenticated RCE in GitLab via regex integer overflow
Is CVE-2026-110264 being exploited?
Not confirmed. CVE-2026-110264 does not appear in CISA's Known Exploited Vulnerabilities catalog, which records only exploitation that has been observed and reported publicly. That is evidence of absence of a report, not evidence the flaw is unattacked. EPSS currently estimates a 1.0% probability of exploitation in the next 30 days.
How severe is CVE-2026-110264?
CVE-2026-110264 is rated Critical with a CVSS score of 10.0. Severity describes how bad exploitation would be, not how likely it is: pair it with exploitation evidence before deciding what to patch first.
Is there a patch for CVE-2026-110264?
Yes. A fix has been recorded for CVE-2026-110264. The vendor advisory is the authority on the exact fixed version — apply it from there rather than from a summary.
What does CVE-2026-110264 affect?
CVE-2026-110264 affects GitLab CE/EE all versions from 7.0 before 18.11.13, 19.0 before 19.0.10, 19.1 before 19.1.9, 19.2 before 19.2.9, and 3 further products or versions. Confirm the exact affected versions against the vendor advisory before deciding you are exposed.
What should I do about CVE-2026-110264?
Upgrade to vendor-patched GitLab versions or apply official patch immediately.
Exploitation status reflects CISA's KEV catalog as we last synced it. Check the catalog directly.
Unauthenticated remote code execution on GitLab server via crafted regular expression integer overflow, allowing full server compromise.
Immediate action required
- affected>= 7.0 and < 18.11.13
- affected>= 19.0 and < 19.0.10
- affected>= 19.1 and < 19.1.9
- affected>= 19.2 and < 19.2.9
- affected>= 19.3 and < 19.3.6
- affected>= 19.4 and < 19.4.3
- affected>= 19.5 and < 19.5.1
As published in the CVE Program record. A version outside these ranges is not a statement that it is unaffected — vendors sometimes understate a range, and distribution-backported builds carry upstream numbers that do not reflect what was patched into them.