# CVE-2026-97229: GitLab Community Edition and Enterprise Edition Integer Overflow or Wraparound > An unauthenticated attacker can execute arbitrary code on the GitLab server by submitting a specially crafted regular expression in CI/CD configurations. - **Severity:** Critical 10.0 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:H/A:H`) - **Exploited in the wild:** Yes, since 29 Oct 2026 (CISA KEV) - **Login needed:** Not needed - **Attackable:** Over the internet - **Victim action needed:** Not needed - **Fix available:** Yes - **Published:** 13 Oct 2026 - **Updated:** 29 Oct 2026 - **Also known as:** ALPINE-CVE-2026-97229, AZL-111074, BELL-CVE-2026-97229, BIT-gitlab-2026-97229, DEBIAN-CVE-2026-97229, GHSA-9hj5-r43h-h3xg, MINI-5prr-qv74-2wp3, MINI-7mmm-7394-v9gw, MINI-8h99-62gf-4gpm, MINI-f975-hwh4-9jjw, MINI-jmpx-5fc7-5qrv, MINI-mf55-78r3-j2cq, MINI-r536-f98c-rgpq, MINI-x53r-cmrx-92ff, MINI-xc85-m65g-cm88, UBUNTU-CVE-2026-97229 ## What is CVE-2026-97229? CVE-2026-97229 is a critical vulnerability in Gitlab Gitlab, published on 13 Oct 2026. An attacker can exploit it over the internet without logging in, with no action from the victim. ### Official description GitLab has remediated an issue in GitLab CE/EE affecting all versions from 19.2 before 19.2.8, 19.3 before 19.3.5, and 19.4 before 19.4.2 that, under certain conditions, could have allowed an unauthenticated user to execute arbitrary code on the GitLab server via a specially crafted regular expression in a CI/CD configuration, due to insufficient regular expression validation. Weakness: CWE-190 (Integer Overflow or Wraparound) ## Which versions are affected by CVE-2026-97229? 1 open source package ship an affected version, including gitlab. It affects 1 product. | Package | Ecosystem | Affected | Fixed in | | --- | --- | --- | --- | | `gitlab` | Bitnami | From 19.2.0 | 19.2.8, 19.3.5, 19.4.2 | Products: Gitlab Gitlab. ## How do I fix CVE-2026-97229? Upgrade gitlab to a fixed version for your release line: 19.2.8, 19.3.5 or 19.4.2. US federal agencies must fix it by 1 Nov 2026. ## Is CVE-2026-97229 being exploited? Yes. Attackers have exploited CVE-2026-97229 in the wild since at least 29 Oct 2026. Public exploit code: - GitLab CI lint integer-overflow RCE PoC for CVE-2026-97229, validated against the official 19.4.1 CE amd64 image (github_poc): https://github.com/jburgess-r7/CVE-2026-97229-PoC - CVE-2026-97229 GitLab CI lint regex integer overflow RCE — InstaBox version matrix reproduction & libruby gadget reverse engineering (github_poc): https://github.com/gandli/cve-2026-97229-lab - CVE-2026-97229 + CVE-2026-110264 — GitLab Onigmo RCE Exploit Toolkit (CVSS 10.0) (github_poc): https://github.com/murat-levi/gitlab-rce-toolkit - CVE-2026-97229 — GitLab CI/CD Regex Compiler RCE (github_poc): https://github.com/AmpedWasTaken/CVE-2026-97229-GitLab-CI-CD-Regex-Compiler-RCE - CVE-2026-97229 an external exploit for GitLab CI lint regex RCE. It is used only against a live GitLab target with permission. It creates a project, pushes a malicious CI configuration, triggers the CI lint endpoint, and receives command output through an HTTP callback. This is for authorized security research only. (github_poc): https://github.com/Noshadi-sec/CVE-2026-97229 - Detection-only triage for GitLab CVE-2026-97229 (and CVE-2026-110264): grade a self-managed GitLab version plus its Ruby, catch the Oct-12-patch and custom-Ruby traps. No payloads, no network probes. (github_poc): https://github.com/foxcornlab/gitlab-onigmo-scanner ## Other vulnerabilities in Gitlab Gitlab - [CVE-2026-85706](https://insights.sbomify.com/CVE-2026-85706/): GitLab Community Edition and Enterprise Edition Path Traversal (critical 10.0, exploited in the wild) - [CVE-2023-7028](https://insights.sbomify.com/CVE-2023-7028/): GitLab Community and Enterprise Editions Improper Access Control (critical 10.0, exploited in the wild) - [CVE-2021-22205](https://insights.sbomify.com/CVE-2021-22205/): GitLab Community and Enterprise Editions Remote Code Execution (critical 10.0, exploited in the wild) - [CVE-2021-39935](https://insights.sbomify.com/CVE-2021-39935/): GitLab Community and Enterprise Editions Server-Side Request Forgery (SSRF) (medium 6.8, exploited in the wild) - [CVE-2021-22175](https://insights.sbomify.com/CVE-2021-22175/): GitLab Server-Side Request Forgery (SSRF) (medium 6.8, exploited in the wild) ## Fix prompt for AI coding agents ```text Check this codebase for CVE-2026-97229 and fix it if it is affected. What it is: CVE-2026-97229 is a critical vulnerability in Gitlab Gitlab, published on 13 Oct 2026. An attacker can exploit it over the internet without logging in, with no action from the victim. Exploitation: Yes. Attackers have exploited CVE-2026-97229 in the wild since at least 29 Oct 2026. Affected packages and fixed versions: - gitlab (Bitnami): affected from 19.2.0; fixed in 19.2.8, 19.3.5, 19.4.2 Task: 1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies. 2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it. 3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead. 4. Run the tests and summarise what changed and why. 5. If nothing in the project is affected, say so and change nothing. Reference: https://insights.sbomify.com/CVE-2026-97229/ (Markdown: https://insights.sbomify.com/CVE-2026-97229/index.md) ``` ## Sources - CVE record: https://www.cve.org/CVERecord?id=CVE-2026-97229 - NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-97229 - OSV: https://osv.dev/vulnerability/CVE-2026-97229 --- From sbomify Insights: https://insights.sbomify.com/CVE-2026-97229/ Summaries are generated and may contain mistakes; the official description above is the record.