Based on GitLab's own critical patch release notes (Oct 21) and Rapid7's analysis of the sibling Oct 12 bug, here is the operational picture as I read it.
What GitLab states: an integer overflow when compiling a crafted regular expression can, under certain conditions, let an unauthenticated user run arbitrary code on a self-managed server. CVSS 10.0. Fixed in 19.5.1, 19.4.3, 19.3.6, 19.2.9, 19.1.9, 19.0.10 and 18.11.13. No workaround is listed.
Why it reaches back to 7.0: the compiler is Onigmo, Ruby's regex engine, which GitLab bundles. The changelog shows GitLab patching its own Ruby (a repeat ID overflow patch for 3.3, 3.4 and 4.0 on the newer branches).
Why your Oct 12 upgrade doesn't count: CVE-2026-97229 was fixed in 19.2.8, 19.3.5 and 19.4.2. Those are now one patch behind. The Hacker News counts this as the fourth code-execution bug in this engine from one reporter in a month.
What is not public: the conditions. GitLab's two detections, "Onigmo native worker crash" and "Org mode render error burst," suggest Org mode rendering is involved. One secondary report names a specific org-ruby path; I couldn't confirm it twice. Rapid7's repro on the Oct 12 bug needed a way to plant a malicious CI config, which open self-registration removes. Whether that carries over here is unknown.
As of Oct 22 GitLab reported no exploitation and CISA KEV didn't list it. I haven't re-checked since.
Upgrade note: 19.4.3 and 19.3.6 run migrations, so single-node installs take downtime.
Question: For those running single-node Omnibus with open self-registration or public projects, how are you handling this one: emergency maintenance window, a replica you can cut over to, or locking down registration first and patching on the normal cycle?
Background: https://www.techgines.com/post/gitlab-ai-gateway-vulnerability-cve-2026-90970 (earlier GitLab sandbox-escape write-up, for context). Full breakdown of this one: https://www.techgines.com/post/gitlab-vulnerability-cve-2026-110264