GitLab fixes two maximum-severity code-execution flaws in ten days, and CISA says the first is being exploited
October 29, 2026 (October 12 to 29, 2026)
On October 12 GitLab patched CVE-2026-97229, an integer overflow in the regular-expression compiler that processes CI/CD pipeline files. It could let an unauthenticated attacker run code on self-managed GitLab CE and EE servers (CVSS 10.0). Rapid7 published a proof of concept on October 13, and Censys counted about 25,800 exposed vulnerable hosts. Alpine Linux says an attacker sent exploit attempts at its own GitLab server on October 20 and 21; the attack failed and Alpine rebuilt the instance. On October 29 CISA added CVE-2026-97229 to its exploited list, with a federal deadline of November 1. On October 21 GitLab fixed a second maximum-severity flaw, CVE-2026-110264, another integer overflow in the same regular-expression compiler; the affected code dates to 2014. GitLab.com is already fixed. GitLab has not said whether the second flaw has been exploited, and it was not on CISA's list as of October 30. Servers patched on October 12 are still affected by it, and there is no workaround. Alpine's experience also shows that upgrading GitLab may not be enough if you run your own Ruby: its image uses standard Ruby, and the flaw was not fixed after it updated to GitLab 19.3.6.
Why it matters
A self-hosted GitLab server holds source code, pipeline settings and deployment secrets, so a takeover can reach well beyond the server itself. Exploit code has been public since October 13, and real attempts followed within a week.
What defenders can take from it
- Upgrade to a release that fixes both flaws, for example 19.5.1, 19.4.3, 19.3.6, 19.2.9, 19.1.9, 19.0.10 or 18.11.13. The October 12 patches do not cover the second flaw.
- If GitLab runs on your own Ruby (a source install or a custom container image), update Ruby as well, because Alpine Linux's instance stayed vulnerable after the GitLab upgrade.
- Keep self-managed GitLab off the public internet where you can. If it was exposed, review recent CI configuration changes and unusual processes on the server, and rotate pipeline secrets if compromise cannot be ruled out.
Sources
- Singapore CSA: critical vulnerability in GitLab (AL-2026-152)
- SOC Prime: CVE-2026-110264, critical GitLab RCE flaw
- Rescana: GitLab CVE-2026-110264 unauthenticated RCE
- CISA: two known exploited vulnerabilities added, October 29
- SecurityWeek: max-severity GitLab vulnerability exploited against Alpine Linux
- BleepingComputer: CISA says max severity GitLab flaw now exploited in the wild
- BleepingComputer: GitLab warns of new max severity code execution vulnerability
- Daily Security Review: public exploit released for GitLab CVE-2026-97229