CVE-2026-97229: GitLab Community Edition and Enterprise Edition flaw exploited in the wild, what we know

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.

• Severity: CRITICAL (CVSS 3.1 10, vector CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:H/A:H).
• Weakness: CWE-190.
• NVD published 2026-10-13, status Analyzed.

Anyone running GitLab Community Edition and Enterprise Edition in the version ranges below. Internet-facing instances are the priority.

• gitlab gitlab: from 19.2.0 up to (not including) 19.2.8.
• gitlab gitlab: from 19.3.0 up to (not including) 19.3.5.
• gitlab gitlab: from 19.4.0 up to (not including) 19.4.2.
• ruby-lang ruby: from 3.3.0 up to (not including) 3.3.13.
• ruby-lang ruby: from 3.4.0 up to (not including) 3.4.12.
• ruby-lang ruby: from 4.0.0 up to (not including) 4.0.8.

Version ranges come from the NVD CPE configuration. Confirm against the vendor advisory before you rely on them.

• Exploited in the wild: added to the CISA Known Exploited Vulnerabilities catalog on 2026-10-29; federal remediation due date 2026-11-01.
• Metasploit module: exploit/multi/http/gitlab_cicd_regexp_rce_cve_2026_97229 (GitLab CI/CD RegExp Integer Overflow Remote Code Execution), disclosure date 2026-10-12.
• Public proof-of-concept code: 7 GitHub repositories from 7 accounts, the first on 2026-10-13.

CISA added CVE-2026-97229 to its Known Exploited Vulnerabilities catalog on 2026-10-29. A KEV listing means CISA has evidence that attackers are using the flaw against real systems, not just that it could be used.

If your business runs GitLab Community Edition and Enterprise Edition, put this at the top of the patch list. CISA gave US federal agencies until 2026-11-01 to deal with it, and that is a sensible deadline for a small business too.

• Patch. Update to a fixed release: gitlab gitlab 19.2.8 or later; gitlab gitlab 19.3.5 or later; gitlab gitlab 19.4.2 or later. These versions come from NVD's configuration data, so confirm them against the advisory from GitLab.
• If you cannot patch yet. Follow CISA's 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.
• Check your exposure. Find out whether GitLab Community Edition and Enterprise Edition can be reached from the internet, for example a VPN portal, an admin login page or a file-transfer site. Your firewall's port-forwarding rules and your IT provider's list of public-facing systems are the quickest places to look. Exposed copies come first.
• When to call IT support. Call your IT support provider now if you run GitLab Community Edition and Enterprise Edition and cannot confirm it is updated, if it was reachable from the internet before you patched it, or if you notice accounts, sign-ins or files you do not recognise. The last two can mean the system was already hit, and checking that properly takes someone who can read the logs.

• EPSS (probability of exploitation activity in the next 30 days): 27.69%, higher than 98% of all scored CVEs (as of 2026-11-03).
• CVERadar threat level: 73/100 (see methodology).
• Likely ATT&CK techniques: T1203 Exploitation for Client Execution (inferred); T1190 Exploit Public-Facing Application (inferred).

1. Find every instance. List where GitLab Community Edition and Enterprise Edition runs, including test, DR and forgotten internet-facing systems, and record the installed version.
2. Upgrade to a fixed release. gitlab gitlab: 19.2.8 or later; gitlab gitlab: 19.3.5 or later; gitlab gitlab: 19.4.2 or later; ruby-lang ruby: 3.3.13 or later. Get the build from the vendor advisory.
3. If you can't patch today, follow CISA's 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.
4. Verify the fix. Re-run the version check on every instance and confirm it reports the fixed build (19.2.8 or later). Re-scan from outside if the service is exposed.
5. Hunt for signs of earlier compromise. If the system was exposed before you patched, assume it may have been hit and check the items below.
6. Rotate credentials stored on or used by the affected system if you cannot rule out compromise, and keep the logs you reviewed.

Detection hints

• T1190 Exploit Public-Facing Application: Review WAF, reverse-proxy and application logs for unusual requests to Community Edition and Enterprise Edition (odd paths, oversized or encoded payloads, bursts of errors), going back to at least 2026-10-13.
• T1203 Exploitation for Client Execution: Exploitation of client or server software usually shows as crashes of the affected process followed by unexpected child processes; check EDR alerts for both.

Detection commands are generic starting points, not CVE-specific signatures. Use the indicators from the vendor advisory when it publishes them.

• NVD: CVE-2026-97229 nvd.nist.gov/vuln/detail/CVE-2026-97229
• CVE.org record www.cve.org/CVERecord?id=CVE-2026-97229
• Vendor link from CISA KEV www.ruby-lang.org/en/news/2026/10/23/regexp-fixes-for-gitlab-cves
• Vendor link from CISA KEV docs.gitlab.com/releases/patches/patch-release-gitlab-19-4-2-released/
• CISA KEV catalog www.cisa.gov/known-exploited-vulnerabilities-catalog
• FIRST EPSS (2026-11-03) api.first.org/data/v1/epss?cve=CVE-2026-97229