CVE-2026-97229
GitLab — GitLab Community Edition and Enterprise Edition Integer Overflow or Wraparound Vulnerability
GitLab · CWE-190 — Integer overflow or wraparound · in CISA KEV since 2026-10-29
EVRS 85 of 100 Immediate
Out-of-Band / Urgent Remediation
Rank 463 of 2,981 tracked
Raised to the floor for a confirmed exploited vulnerability.
Why it scores 85
Evidence available: 6 of 7 signalsListed in the CISA KEV catalog, and an EPSS probability of 0.184.
- CISA KEVApplied
- RansomwareDid not apply
- Vendor exploitationDid not apply
- EPSSApplied
- Microsoft Exploitability IndexNot applicable
- Pre-patch disclosureNo data
- KEV recencyApplied
- CVSSApplied
The band answers “how soon”, not “how bad”. No data for: Pre-patch disclosure. Why some signals show no data
Fix
Patch or fixed version identifiedCISA required action
- Other products can potentially be affected by the same underlying Ruby/Onigmo Integer Overflow issue in CI/CD Regular Expression Compiler. For more information please see
- docs.gitlab.com/…/patch-release-gitlab-19-4-2-released
- BOD 26-04
- Forensics Triage Requirements
- nvd.nist.gov/…/CVE-2026-97229
Fixed in
Red Hat Hardened Images -> ruby3.4-0:3.4.12-33.1.hum1@aarch64 | Red Hat Hardened Images -> ruby4.0-0:4.0.9-41.hum1@aarch64 | Red Hat Hardened Images -> ruby3.3-0:3.3.13-23.8.hum1@aarch64 | openSUSE Tumbleweed -> libruby4_0-4_0-0:4.0.9-1.1.aarch64
Affected versions
- gitlab
>= 19.2.0 < 19.2.8>= 19.3.0 < 19.3.5>= 19.4.0 < 19.4.2
Remediation
Apply mitigations in accordance with vendor instructions, ensuring compliance with CISA’s BOD 26-04 Prioritizing Security Updates Based on Risk (see URL in Notes) guidance and CISA’s “Forensics Triage Requirements” (see URL in Notes). Follow applicable BOD 26-04 guidance for cloud services or discontinue use of the product if mitigations are unavailable. Stakeholders are responsible for evaluating each asset's internet exposure and ensuring adherence to BOD 26-04 patching guidelines.
Fixed versions from NVD.
Evidence
Each value with its source| Measure | Value | Source |
|---|---|---|
| CVSS base scoreHow severe the flaw is in itself. It does not say how likely an attack is. | 9.8 | Red Hat |
| FIRST EPSSFIRST's estimate of the chance this is exploited in the next 30 days, and how that ranks against all CVEs. | 0.184 (97.2nd pctl) | FIRST EPSS |
| Actively exploitedWhether a source of record has confirmed attacks using it in the wild. | Confirmed | CISA KEV |
| Ransomware campaign useWhether CISA has seen ransomware operators use it. | Unknown or none | CISA KEV |
| CISA remediation deadlineThe date US federal agencies must have fixed or mitigated it. | 2026-11-01 · CISA federal deadline in 2 days | CISA KEV |
| Public exploit moduleA module existing is not the same as active exploitation. | None known | Metasploit |
| EUVD cross-referenceENISA's record: CVSS 10.0 (v3.1), assigned by GitLab. | Listed | ENISA EUVD |
Description
NVDGitLab 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.
What CISA says to do