Critical code to be run remotely without a login in GitLab
What happened
CVE-2026-97229 (the public catalogue number for a specific software flaw): Critical Unauthenticated Remote Code Execution in GitLab, Rapid7 Blog announced. Overview On October 12, 2026, GitLab published a critical patch release for CVE-2026-97229 , an integer overflow or wraparound ( CWE-190 ) in the CI/CD (the automated pipeline that tests and ships code changes) regular expression compiler affecting GitLab Community Edition (CE) and Enterprise Edition (EE). GitLab assigned the vulnerability a CVSSv3.1 score of 10.0 .
Under certain conditions, a remote attacker can execute arbitrary code on an affected GitLab server through a specially crafted regular expression stored in a malicious CI/CD configuration. While the vendor supplied CVSS score indicates that exploitation is fully unauthenticated, in reproducing the exploit it was noted that an attacker must have a mechanism to plant a malicious CI/CD configuration to a repository prior to triggering the vulnerability.
On GitLab instances where new users can self register and create projects, this constraint is removed. The vulnerability affects self-managed GitLab instances across all deployment types.
Sources & evidence
- Rapid7 Blog Primary / official
CVE-2026-97229: Critical Unauthenticated Remote Code Execution in GitLab ↗
https://www.rapid7.com/blog/post/etr-cve-2026-97229-critical-unauthenticated-remote-code-execution-in-gitlab