GitLab CE and EE flaw exploited for unauthenticated remote code execution
On 29 October 2026, CISA added CVE-2026-97229, an integer overflow in GitLab Community Edition and Enterprise Edition that allows unauthenticated remote code execution, to its Known Exploited Vulnerabilities catalogue. Organisations running self-managed GitLab are concerned, as are other products that rely on the Ruby/Onigmo regular expression engine.
What to do now
- Product
- GitLab Community Edition and Enterprise Edition
- Affected versions
- Vulnerable versions not specified by the source.
- Fixed in
- GitLab 19.4.2 patch release notes referenced by CISA.
- CVE
- CVE-2026-97229
CISA has listed CVE-2026-97229 in its Known Exploited Vulnerabilities catalogue, which only includes flaws with observed exploitation. The flaw affects GitLab Community Edition and GitLab Enterprise Edition. It is an integer overflow or wraparound (CWE-190) caused by insufficient validation of regular expressions.
An attacker can place a specially crafted regular expression in a CI/CD configuration and run arbitrary code on the GitLab server. According to CISA, no authentication is required. Someone with no account could therefore take over the server that holds source code, pipelines and often deployment secrets.
CISA notes that the root cause sits upstream, in the Ruby/Onigmo regular expression compiler used during CI/CD processing. Other products built on that component may also be affected. The agency points to a Ruby project advisory on regular expression fixes dated 23 October 2026 and to GitLab's 19.4.2 patch release notes. The source does not list the vulnerable versions and does not say whether a fix exists for every supported branch.
US federal agencies must apply the vendor's mitigations by 1 November 2026 under directive BOD 26-04. CISA also requires forensic triage, so exposed servers have to be checked for compromise rather than simply patched. If no mitigation is available, agencies must stop using the product. Whether the flaw has been used in ransomware campaigns is currently unknown.
What to do now
- Inventory every self-managed GitLab CE and EE instance, starting with those reachable from the internet.
- Apply GitLab's fix, using the 19.4.2 patch release notes referenced by CISA and the vendor's instructions for your release branch.
- Check exposed servers for signs of compromise, including CI/CD configurations with unusual regular expressions and unexpected processes or files.
- As a precaution, rotate tokens, keys and CI/CD secrets stored on any instance that was exposed before patching.
- Find out whether other Ruby applications in your environment use Onigmo and track the regular expression fixes announced by the Ruby project.