NewApp Monitoring is liveSign up free
AgentbeamBeta
Known exploited vulnerability · GitLab

CVE-2026-97229: GitLab Community Edition and Enterprise Edition Integer Overflow or Wraparound Vulnerability

criticalCVSS 3.1 10.0Exploited

GitLab CE/EE has a critical flaw (CVSS 10.0) that, under certain conditions, lets an unauthenticated attacker run code on the GitLab server through a crafted regular expression in a CI/CD configuration. CISA lists it as exploited in the wild. Fixed in 19.2.8, 19.3.5 and 19.4.2. GitLab.com and Dedicated are already patched. Self-managed instances must upgrade now.

Published Oct 13, 2026 · Updated Nov 2, 2026 · Analysis Oct 30, 2026

What an attacker can do

GitLab describes an integer overflow in how the CI/CD regular expression handling validates patterns. Insufficient validation of a crafted expression in a CI/CD configuration can corrupt memory and lead to code execution as the GitLab service on the server. GitLab says it can be triggered by an unauthenticated user under certain conditions. The vendor does not spell out those conditions.

The attacker needs network access to the instance. No account or user interaction is needed, and the scope is changed, which is why the score is 10.0. Code execution on a GitLab server exposes source code, CI/CD variables and tokens, runner registration secrets, deploy keys and anything the server can reach. A compromised GitLab is a strong foothold into build and release pipelines.

CISA added the CVE to its Known Exploited Vulnerabilities catalog on 2026-10-29, so exploitation is confirmed. The EPSS score is high as well.

Who is affected

Self-managed GitLab Community Edition and Enterprise Edition from 19.2 before 19.2.8, from 19.3 before 19.3.5, and from 19.4 before 19.4.2. GitLab.com and GitLab Dedicated are already patched. The patch release page does not say whether 19.1 and earlier are affected, so do not treat them as safe without checking with GitLab.

The version shows in the GitLab UI under Help, or in the footer of the Admin Area. On the server:

sudo gitlab-rake gitlab:env:info

How to fix it

Upgrade to 19.2.8, 19.3.5 or 19.4.2, or later, matching your current branch. GitLab's only recommendation is to upgrade as soon as possible, and the patch release page lists no workaround.

CISA's required action: apply mitigations in accordance with vendor instructions, following BOD 26-04 (Prioritizing Security Updates Based on Risk) and CISA's Forensics Triage Requirements. Follow the BOD 26-04 guidance for cloud services, or stop using the product if mitigations are unavailable. Stakeholders must assess each asset's internet exposure. The due date is 2026-11-01, and it binds US federal agencies.

If an instance was exposed to the internet and unpatched, upgrade first, then rotate CI/CD variables, runner tokens and deploy keys.

CISA 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.

How to tell if you were hit

GitLab published six threat detections for self-managed instances: Onigmo native worker crash, Graphql cilint hostile regexp, ci regexp oversized non ascii path, ci regexp guard rejection, ci lint workhorse worker crash, and ci lint scripted client error burst. Their definitions are in GitLab's security TLDR repository, linked from the patch release page. Also check for unexpected worker crashes, odd child processes of the GitLab services, new users, tokens or runners, and unusual CI lint or GraphQL requests from unauthenticated clients. CISA's Forensics Triage Requirements apply to federal agencies.

Original advisory

From the National Vulnerability Database. This product uses the NVD API but is not endorsed or certified by the NVD.

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.

Questions

Is CVE-2026-97229 exploited in the wild?

Yes. CISA added it to the Known Exploited Vulnerabilities catalog on 2026-10-29.

Which GitLab versions fix it?

19.2.8, 19.3.5 and 19.4.2. Upgrade within your branch to the matching version or a later one.

Does the attacker need a GitLab account?

GitLab says an unauthenticated user could trigger it under certain conditions. The vendor does not detail those conditions, so treat any reachable unpatched instance as exposed.

Is there a workaround?

The patch release page lists none. Upgrading is the only recommended action. GitLab.com and GitLab Dedicated are already patched.

References

How this page is made: the data panel comes from the GitHub Advisory Database, CISA’s KEV catalog, the NVD and FIRST EPSS, and updates twice a day. The analysis is written by an AI model from the sources listed above and checked by automated rules before it is published. Check versions against the vendor's advisory before you act. Methodology

Coverage on the Beam blog

More GitLab vulnerabilities

All GitLab entries