GitLab warns of max severity code execution vulnerability
GitLab warns of max severity code execution vulnerability (CVE-2026-97229) in CI/CD Regular Expression Compiler.
Run GitLab?
Get an email when a reviewed story names GitLab, usually within the hour.
Free. Your list stays private and never appears in a subject line. One click stops it. How Vendor Watch worksPrivacy
Summary
GitLab has issued an urgent warning for a critical code execution vulnerability, CVE-2026-97229, affecting its CI/CD Regular Expression Compiler. The flaw, caused by an integer overflow, allows unauthenticated remote attackers to run arbitrary code on vulnerable GitLab servers by submitting a specially crafted regular expression. GitLab has released patches for affected versions and urges all self-managed installations to update immediately.
The lesson from this incident
Full lessonA maximum-severity integer overflow vulnerability in GitLab's CI/CD Regular Expression Compiler allows unauthenticated remote attackers to execute arbitrary code on unpatched self-managed GitLab servers. Because no authentication is required to exploit this flaw, the attack surface is extremely broad — any internet-exposed GitLab instance is at risk. This underscores the danger of delaying patches on critical developer infrastructure, which often holds source code, secrets, and pipeline credentials. Organizations without a formal emergency patching process are especially vulnerable, as the window between public disclosure and active exploitation is shrinking.
What helps against this
How we list vendors- Vulnerability scanning and prioritisation
You know which systems are vulnerable, and which ones to fix first.
- Automated patch management
Known holes get closed in days, not months.
- Endpoint detection and response (EDR and XDR)
Malware and hands-on-keyboard attackers on laptops and servers get spotted and stopped.
Indicators of Compromise
- cve — CVE-2026-97229
- cve — CVE-2026-0723
- cve — CVE-2026-85706