CVE-2026-97229 — gitlab
CRITICALCVE-2026-97229 is a critical-severity (CVSS 10) CWE-190 vulnerability. It is in CISA's Known Exploited Vulnerabilities catalog (added 2026-10-29) — treat it as actively exploited and patch now. A fix is available — see the affected versions and patch details below.
Integer Overflow or Wraparound in GitLab
Exploitation Status
Actively exploited in the wild
- Confirmed by CISA's Known Exploited Vulnerabilities catalog on 2026-10-29. Federal agencies were required to remediate by 2026-11-01.
- CISA assesses this as automatable — exploitation doesn’t require manual, per-target effort, which raises the odds of mass scanning and opportunistic attacks.
- A successful exploit gives an attacker total control of the affected component, not partial access.
Exploitation and automatability from CISA (KEV catalog and SSVC triage) for CVE-2026-97229.
EPSS Exploitation Probability
Probability of exploitation in the next 30 days, from FIRST.org EPSS.
How urgent is this, really
CVE-2026-97229 by exploitation likelihood (EPSS) against impact (CVSS). Outside the shaded patch-first corner.
Where this sits among everything scored
Of 398,142 CVEs with a current EPSS score, this one falls in the 10–50% band (highlighted). Counts from FIRST.org, log-scaled.
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.
Affected Products
gitlabgitlabDetection & mitigation playbook
VulnerabilityDetect
Identify every host running the affected component and compare the installed build against the fixed version below — for source-built or distro-packaged software the version string, not a lockfile, is the source of truth (`dpkg -l`, `rpm -q`, or the binary's own `--version`).
Fix
Upgrade the affected component to the fixed release for CVE-2026-97229, or apply your distribution's backported patch — distro builds are often patched at an older version number, so check your vendor's advisory rather than the upstream version alone.
Workarounds
If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.
Fixing This On Your OS
If you run this on a Linux distribution, patch through your package manager against the distro's own security advisory below — it tracks the exact backported fix for your release, which can ship on a different timeline (and sometimes a different severity) than the upstream project.
Red Hat has rated the impact of these flaws as Moderate for the Ruby packages shipped in Red Hat Enterprise Linux. The Ruby packages provide a language interpreter and standard library and do not accept external input on their own; these flaws are reachable only when an application compiles a regular expression…
To mitigate this vulnerability, do not compile regular expressions from untrusted sources. Standard safeguards such as Regexp.timeout or limiting the length of the input pattern do not protect against this issue.Source: Red Hat security advisory for CVE-2026-97229 (CC BY 4.0)
| Product | Fixed in | Advisory |
|---|---|---|
| Red Hat Hardened Images | ruby3-4-main-3.4.12-33.1.hum1 | RHSA-2026:88861 |
| Red Hat Hardened Images | ruby4-0-main-4.0.9-41.hum1 | RHSA-2026:88865 |
| Red Hat Hardened Images | ruby3-3-main-3.3.13-23.8.hum1 | RHSA-2026:88880 |
Frequently Asked Questions
Is CVE-2026-97229 in your dependencies?
Find it across , including transitive dependencies.