Back Daily.Dev Over 1000 GitLab servers vulnerable to ongoing RCE attacks
Over 1,000 internet-exposed GitLab servers remain unpatched against a maximum-severity remote code execution flaw under active attack. The bug, CVE-2026-97229, is an integer overflow in the CI/CD Regular Expression Compiler that could allow an unauthenticated user to run arbitrary code via a specially crafted regex in a CI/CD configuration. GitLab patched it three weeks ago in versions 19.4.2, 19.3.5, and 19.2.8. CISA added the flaw to its Known Exploited Vulnerabilities catalog and ordered federal agencies to secure their servers by Sunday. Shadowserver also counts over 11,300 instances still vulnerable to a separate flaw, CVE-2026-110264, out of roughly 39,000 GitLab instances it sees daily.
Questions this post answers
CVE-2026-97229 is a maximum-severity integer overflow vulnerability in GitLab's CI/CD Regular Expression Compiler, the component that parses regular expressions in pipeline configuration files. Under certain conditions it lets an unauthenticated attacker execute arbitrary code on the GitLab server using a specially crafted regular expression placed in a CI/CD configuration, due to insufficient regex validation. Teams running self-managed GitLab can track exploited CVEs like this one on daily.dev before they hit production.
GitLab fixed the flaw in Community Edition and Enterprise Edition versions 19.4.2, 19.3.5, and 19.2.8, released on October 12. GitLab.com was already running the patched version at release time, and GitLab Dedicated customers did not need to take any action. Self-managed installations were strongly urged to upgrade immediately. Developers planning a GitLab upgrade can follow patch advisories like this on daily.dev.
Threat watchdog Shadowserver reported tracking over 1,000 internet-exposed GitLab instances still vulnerable to CVE-2026-97229, despite patches being available for three weeks, and separately found more than 11,300 instances still vulnerable to CVE-2026-110264, out of roughly 39,000 GitLab instances it scans daily. Security teams gauging real-world patch gaps can follow exploitation data like this on daily.dev.
The full story
This article is one source in a clustered incident — the cluster page carries the summary, timeline and every other outlet covering it.
