Nullify

Lorem ipsum dolor sit amet, consectetur adipiscing elit. Suspendisse varius enim in eros elementum tristique. Duis cursus, mi quis viverra ornare, eros dolor interdum nulla, ut commodo diam libero vitae erat. Aenean faucibus nibh et justo cursus id rutrum lorem imperdiet. Nunc ut sem vitae risus tristique posuere.

Lorem ipsum dolor sit amet, consectetur adipiscing elit. Suspendisse varius enim in eros elementum tristique. Duis cursus, mi quis viverra ornare, eros dolor interdum nulla, ut commodo diam libero vitae erat. Aenean faucibus nibh et justo cursus id rutrum lorem imperdiet. Nunc ut sem vitae risus tristique posuere.

Lorem ipsum dolor sit amet, consectetur adipiscing elit. Suspendisse varius enim in eros elementum tristique. Duis cursus, mi quis viverra ornare, eros dolor interdum nulla, ut commodo diam libero vitae erat. Aenean faucibus nibh et justo cursus id rutrum lorem imperdiet. Nunc ut sem vitae risus tristique posuere.

Home
›
Incidents
›
GitLab CVE-2026-97229: Exploited Code Execution Through CI Regular Expressions
Exploited CVE
Adjacent

GitLab CVE-2026-97229: Exploited Code Execution Through CI Regular Expressions

A crafted regular expression in a GitLab CI configuration could trigger an integer overflow in Ruby's regex engine and run code on self-managed servers.

Nullify Team
·
Disclosed
October 29, 2026
·
Updated
November 17, 2026

What is GitLab CVE-2026-97229?

GitLab's patch release notes say that under certain conditions, an unauthenticated user could execute arbitrary code on a GitLab server with a specially crafted regular expression in a CI/CD configuration, because regex validation was insufficient. The root cause is an integer overflow in Onigmo, the regular expression engine in Ruby. GitLab released fixes on October 12, 2026 and rates the flaw CVSS 3.1 10.0.

CISA added CVE-2026-97229 to its Known Exploited Vulnerabilities catalog on October 29, 2026, with a November 1 due date. The Ruby project published fixed Ruby releases and says other Ruby apps are affected only if they compile attacker-controlled strings into regular expressions.

Which GitLab and Ruby versions are affected?

  • Self-managed GitLab CE and EE from 19.2 before 19.2.8, 19.3 before 19.3.5 and 19.4 before 19.4.2. GitLab.com and Dedicated are already patched.
  • Ruby: fixed in 4.0.9, 3.4.12 and 3.3.13, for apps that build regular expressions from untrusted input.
  • Other products that use the same Ruby and Onigmo code, which CISA notes may be affected.

How to check if you're affected

  1. Check each self-managed GitLab instance's version.
  2. Run the threat detections GitLab published with the release, such as Onigmo worker crashes and hostile regular expressions in CI lint requests.
  3. For other Ruby apps, run ruby -v and search for Regexp.new, Regexp.union, Regexp.compile or interpolation that takes user input.

What to do now

  1. Upgrade GitLab to 19.4.2, 19.3.5 or 19.2.8 or later. GitLab lists no workaround.
  2. Upgrade Ruby to 4.0.9, 3.4.12 or 3.3.13 in other apps, or stop compiling regular expressions from untrusted input.
  3. Don't rely on Regexp.timeout or pattern length limits. Ruby says neither protects against these bugs.

Why user-supplied regular expressions are dangerous

Letting users submit patterns hands them a small program for your regex engine to compile and run. Beyond slow patterns, engine bugs like this one turn a pattern into memory corruption. If a feature needs user-defined matching, prefer a restricted syntax, or compile patterns in an isolated worker with strict limits, and keep the regex engine patched like any other parser.

Where Nullify fits

How Nullify Covers This Class of Attack

Adjacent
Known Exploited Vulnerabilities Catalog

Nullify is threat-aware: when an actively exploited vulnerability affects technologies you use, related findings move up your backlog and serious disclosures trigger a threat investigation. Patching self-hosted platforms stays with the team that runs them.

This is a patch for a self-hosted platform, usually owned by an IT or platform team.

Frequently Asked Questions

Which GitLab versions fix CVE-2026-97229?

GitLab 19.4.2, 19.3.5 and 19.2.8, released October 12, 2026. GitLab.com and GitLab Dedicated were already patched, and GitLab lists no workaround for self-managed installs, so upgrading is the only fix.

Does CVE-2026-97229 affect other Ruby apps?

Ruby says apps are affected only if they compile attacker-controlled strings with Regexp.new, Regexp.union, Regexp.compile or interpolation. Upgrade to Ruby 4.0.9, 3.4.12 or 3.3.13, because Regexp.timeout doesn't protect against it.

Is CVE-2026-97229 exploited in the wild?

Yes. CISA added CVE-2026-97229 to its Known Exploited Vulnerabilities catalog on October 29, 2026, which means it has evidence of active exploitation. It gave US federal civilian agencies until November 1 to fix it. Treat exposed self-managed GitLab instances as urgent.

Update Log

  • Nov 17, 2026: page published from the primary sources linked above.

Check your own code for the bug behind this incident

Nullify's AI harness finds, proves and fixes the same class of vulnerability in your code and dependencies, and hands your team a merge-ready pull request.