GitLab Community Edition and Enterprise Edition
CVE-2026-97229
GitLab Community Edition and Enterprise Edition contain a integer overflow or wraparound vulnerability that could allow 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 this means for your business
- It affects GitLab Community Edition and Enterprise Edition. It matters if your company, or a supplier that handles your data, runs it.
- Attackers are already using it. CISA added it to its list of flaws used in real attacks on 29 October 2026.
- An attacker can use it remotely, over a network, without a login, and without anyone at your company clicking anything.
- FIRST's prediction model gives it a 27% chance of attack attempts being seen in the next 30 days, ranking above 98% of all known flaws.
What to do
- 1Check whether your company or your suppliers run GitLab Community Edition and Enterprise Edition, and which version. The affected versions are listed further down this page.
- 2If you do, apply the vendor's fix. A patch or vendor advisory has been published.
- 3Treat it as urgent. US federal agencies must fix it by 1 November 2026. That deadline does not apply to private companies, but it shows how seriously CISA takes it.
- 4Because attackers have used it, check the affected systems for signs of a break-in, not only for the update.
Fastnexa security experts
Attackers are already using this flaw. Is your GitLab Community Edition and Enterprise Edition exposed?
Tell us where you run GitLab Community Edition and Enterprise Edition and a Fastnexa penetration tester will check whether this flaw, or others like it, can be used against your websites, apps and network.
The full test is free for our first 10 founding clients until 31 December 2026. See the offer
Think you’ve already been hit? Don’t wait on a form: call or WhatsApp +1 (732) 454 2616. We reply within 1 hour, 24/7. Emergency help →
Required action
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.
CISA’s wording, unedited. The notes it mentions are in CISA’s catalogue entry.
Scoring
- CVSS
- 10.0 (v3.1)
- Vector
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:H/A:H- Weakness
- CWE-190
- Assigned by
- cve@gitlab.com
Dates
- Published
- 2026-10-29
- Last modified
- 2026-10-14
- Added to KEV
- 2026-10-29
- Remediation due
- 2026-11-01
- Sources
- CISA KEV, NVD
Affected products
- Gitlab Gitlab19.2.0 - 19.2.8, 19.3.0 - 19.3.5, 19.4.0 - 19.4.2
As listed in the NVD configuration data. Not a statement about your estate.
Coverage
- Max-Severity GitLab Vulnerability Exploited Against Alpine LinuxSecurityWeek · 2026-10-30
- CISA Adds Actively Exploited GitLab RCE and Cisco Firewall DoS Flaws to KEVThe Hacker News · 2026-10-30
- Attacker Tried to Exploit Alpine Linux’s GitLab via CVSS 10.0 Flaw Its Ruby Left OpenThe Hacker News · 2026-10-29
- Rapid7 Analysis: GitLab CI/CD Regex Integer Overflow (CVE-2026-97229)Rapid7 Blog · 2026-10-16