CVE-2026-97229: GitLab CE/EE, is it exploitable where you run it
Code called: yesReached: openControl in front: noExploitation known: yesWalk it through the four questions
What the flaw is
GitLab lets users write CI/CD rules that match file paths with regular expressions. GitLab compiles and matches them with Ruby's Onigmo engine. In some cases the compiled form of a pattern grows past the size of a 32-bit integer and the size wraps around (CWE-190, integer overflow). The wrap lets the engine run past the end of its buffer, which an attacker can turn into code execution on the GitLab server. GitLab's detection guidance says the code runs as the git user.
That user can read and write every repository on the instance and can read the secrets file, all CI/CD variables, runner tokens and access tokens. GitLab rates the flaw 10.0 (CVSS base score), with scope changed, and says an unauthenticated user can exploit it under certain conditions. GitLab has not published those conditions, and its detection guidance points at CI lint, GraphQL and pushed CI configuration, which in practice need an account, a token or a public project. Treat both as possible until GitLab says otherwise.
This CVE is a bypass. GitLab 19.4.1 added input checks for the earlier CVE-2026-93577, and CVE-2026-97229 gets past them, so 19.4.1 is still affected. The Ruby project fixed the underlying engine bugs in its own releases of 22 and 23 Oct 2026 (4.0.8 on the 22nd; 4.0.9, 3.4.12 and 3.3.13 on the 23rd) and says they matter to any application that compiles regular expressions from attacker-controlled text. Johan Carlsson (joaxcar) reported the flaw through GitLab's bug bounty program.
Are you exposed: each condition and how to check it
| Condition for exposure | How to check it on your system |
|---|---|
| the instance is self-managed GitLab CE or EE (not GitLab.com or GitLab Dedicated, which GitLab patched itself) and runs 19.2.0 to 19.2.7, 19.3.0 to 19.3.4 or 19.4.0 to 19.4.1 | Omnibus: head -1 /opt/gitlab/version-manifest.txt, or sudo gitlab-rake gitlab:env:info. Package: dpkg -l gitlab-ee gitlab-ce or rpm -q gitlab-ee gitlab-ce. Docker: docker exec |
| an attacker can reach the web interface or API and can hold an account or token, or use a public project, to reach CI lint, GraphQL or pipeline processing; GitLab rates the flaw as needing no privileges but has not published the exact conditions, so treat any open path to those features as exposure | Find the address in /etc/gitlab/gitlab.rb (external_url). From a host outside your trusted network test with curl -sI |
| a source install runs a system Ruby older than 4.0.8, 3.4.12 or 3.3.13 | Run ruby -v and compare with 4.0.8 (4.0.9 recommended), 3.4.12 or 3.3.13. Omnibus and Docker packages bundle a Ruby that the GitLab upgrade patches. |
Affected and fixed versions
| Product line | Affected | First fixed version |
|---|---|---|
| GitLab 19.4 (CE and EE, self-managed) | 19.4.0 and 19.4.1 | 19.4.2 |
| GitLab 19.3 (CE and EE, self-managed) | 19.3.0 to 19.3.4 | 19.3.5 |
| GitLab 19.2 (CE and EE, self-managed) | 19.2.0 to 19.2.7 | 19.2.8 |
| GitLab 19.1 and earlier | Not listed as affected by this CVE | Not applicable to this CVE |
| GitLab.com and GitLab Dedicated | Patched by GitLab before the release | No action |
| Ruby (source installs with a system Ruby) | Before 4.0.8, 3.4.12 or 3.3.13 for this flaw | 4.0.8 (released 22 Oct 2026), 3.4.12 and 3.3.13; Ruby recommends 4.0.9, 3.4.12 and 3.3.13 |
If the fix cannot go in yet
- Upgrade to GitLab 19.4.2, 19.3.5 or 19.2.8 or later, and prefer the newest patch of your minor version. 19.4.1 is not enough. GitLab's release notes list no workaround. Cost: a single-node upgrade restarts GitLab services, so plan a maintenance window and back up first.
- Until the upgrade, limit who can create accounts and personal access tokens on the instance. This is GitLab's own prevention advice in its detection guidance. Cost: new users need an invitation or admin approval, and automation that creates tokens needs an administrator. It narrows who can reach the flaw but does not remove it.
- Restrict network access to the GitLab web and API ports to trusted networks or a VPN. This is general hardening, not a GitLab instruction. Cost: contributors and runners outside those networks lose access.
What to look for
- GitLab released six detections for self-managed customers, published in its security-oss tldr repository. Workhorse log (Omnibus: /var/log/gitlab/gitlab-workhorse/current): a 502 with 'badgateway: failed to receive response: EOF' on POST /api/v4/projects/:id/ci/lint or /api/graphql, with a large read_bytes value and a correlation_id that is missing from api_json.log and graphql_json.log. GitLab calls this the highest-confidence signal.
- application_json.log: WARN lines from Gitlab::Ci::Build::Rules::Rule::Clause::RegexpMatcher such as 'regexp rejected at compile time', 'rules:exists regexp match timed out' or 'regexp total time budget exceeded', with the pattern in the extra.regexp field. graphql_json.log: ciLint mutation requests whose logged variables carry oversized or unusual regular expression constructs. api_json.log: several 5xx responses on POST /api/v4/projects/:id/ci/lint from a raw scripted client such as python-urllib, python-requests, curl or Wget.
- Host signs: [BUG] crash reports in puma_stderr.log (Omnibus: /var/log/gitlab/puma/puma_stderr.log) with frames from the org-ruby gem or Onigmo (onig_compile, compile_tree, match_at); 'A worker terminated, shutting down the cluster' in the Sidekiq log (/var/log/gitlab/sidekiq/current); API requests with a repository file path near the 255-byte limit that has a non-ASCII byte in its last segment. GitLab notes a successful exploit can be quiet, so a clean log does not prove safety.
- If you find signs of code execution, GitLab says to treat the instance as compromised: rotate the secrets in gitlab-secrets.json, all CI/CD variables, runner tokens and access tokens. Hunt for files owned by git in /tmp, unexpected child processes of Puma or Sidekiq, and unexpected outbound connections. CISA's KEV entry marks forensic triage as Yes, so preserve the Workhorse, api_json, graphql_json and application_json logs first.
The earliest dated mark of exploitation is CISA's, on 13 Oct 2026, 1 day after disclosure; exploitation may have begun earlier.
Exploitation reported so far
GitLab names no victims and no date of first use, and no vendor or researcher report describes an attack. A public exploit module titled as a GitLab RCE via CI Lint for this CVE is in the Metasploit framework, which lowers the effort for any attacker who can reach an unpatched instance.
Why attack-path analysis settles it
Exposure needs the build to be unfixed and then a route for an attacker to the CI lint, GraphQL or pipeline paths: network reach to the web and API ports, then an open sign-up, a token or a public project. The version read settles the first part. Mapping who can reach the instance and create accounts or tokens settles the second, which GitLab has not described. KEV and a public exploit module mean a reachable instance on an unfixed build should be patched and checked for compromise at once.
Related pages
Sources
- CVE-2026-97229: NVD record, read 19 Nov 2026
- CVE-2026-97229: CISA KEV entry (feed version 2026.11.18), read 19 Nov 2026
- CVE-2026-97229: GitLab critical patch release notes 19.4.2, 19.3.5, 19.2.8 (vendor advisory), read 19 Nov 2026
- CVE-2026-97229: Ruby security note on regexp compilation fixes related to GitLab CVEs (updated 17 Nov 2026), read 19 Nov 2026
- CVE-2026-97229: GitLab security-oss detections for CVE-2026-97229 (GitLab detection guidance), read 19 Nov 2026
- CVE-2026-97229: GitLab Workhorse worker crash detection (GitLab detection guidance), read 19 Nov 2026
- CVE-2026-97229: GitHub API record for Metasploit pull request 22017 (title and dates only), read 19 Nov 2026
- CVE-2026-97229: Ruby release list (4.0.8 dated 22 Oct 2026), read 19 Nov 2026
Last reviewed 19 Nov 2026.