Menu
hands typing on a laptop keyboard

CISA confirms active exploitation of CVSS 10.0 GitLab vulnerability

Posted on 18 November 2026

Reading time 3 minutes

What happened?

The U.S. Cybersecurity and Infrastructure Security Agency (CISA) has added CVE-2026-97229 to its Known Exploited Vulnerabilities (KEV) Catalog after confirming active exploitation in the wild.

CVE-2026-97229 is an integer overflow vulnerability affecting GitLab Community Edition (CE) and Enterprise Edition (EE). The flaw - which was originally reported by a security researcher through GitLab’s HackerOne bug bounty programme - exists within GitLab’s CI/CD Regular Expression Compiler, which parses, compiles and evaluates regular expressions contained within pipeline configuration files, and carries the maximum CVSS score of 10.0.

Under certain conditions, insufficient regular expression validation can allow an unauthenticated attacker to execute arbitrary code on a GitLab server by submitting a specially crafted regular expression within a CI/CD configuration; successful exploitation could therefore provide an attacker with control over an affected GitLab server without requiring valid credentials or user interaction. A proof-of-concept (PoC) exploit is also available, lowering the barrier for attackers to exploit unpatched instances.

The vulnerability affects GitLab CE/EE versions 19.2 before 19.2.8, 19.3 before 19.3.5 and 19.4 before 19.4.2. GitLab-managed infrastructure, including GitLab.com and GitLab Dedicated, remains patched, meaning the primary exposure relates to self-managed instances that have not been updated.

So what?

CVE-2026-97229 presents a particularly dangerous combination of characteristics - it can be exploited remotely, requires no authentication or user interaction, and can result in arbitrary code execution on the affected GitLab server. GitLab is commonly positioned at the centre of software-development and deployment processes, meaning that a compromise affecting the platform may therefore extend beyond the GitLab server itself, particularly where CI/CD pipelines have access to cloud environments, build systems or production credentials.

CISA’s KEV designation is also significant because it is based on evidence of real-world exploitation rather than severity alone. BOD 26-04 requires federal agencies to prioritise the rapid remediation of high-risk KEV vulnerabilities affecting publicly exposed assets where exploitation could provide total control of the asset. The directive also establishes expectations for determining whether threat actors compromised affected systems before patches were applied. The remediation deadline provided to federal agencies was 1 November 2026.

While Binding Operational Directive (BOD) 26-04 applies specifically to U.S. Federal Civilian Executive Branch agencies, KEV inclusion should be treated as a strong prioritisation signal by all organisations.

What should I do?

Organisations operating self-managed GitLab instances should treat CVE-2026-97229 as an urgent patching and compromise-assessment priority.

  • Identify and patch affected instances: Confirm whether self-managed GitLab CE or EE is deployed, and immediately upgrade any instances running 19.2 before 19.2.8, 19.3 before 19.3.5, or 19.4 before 19.4.2 to the fixed version or later.
  • Prioritise internet-facing systems: Self-managed instances exposed to the internet should receive immediate attention, and external exposure should be restricted where it is not operationally required.
  • Review for prior compromise: Patching removes the vulnerability but does not show whether it was previously exploited - where an instance was exposed before updating, conduct a retrospective compromise assessment, including unusual or unauthorised CI configurations, specially crafted regular expressions, unexpected pipeline activity and unexplained worker-process crashes.
  • Assess connected infrastructure: Review the permissions, credentials and secrets available to the instance and its CI/CD pipelines, and where compromise is suspected, rotate potentially exposed credentials from a trusted environment.
  • Consider rebuilding compromised systems: Where evidence indicates exploitation, or where compromise cannot be safely ruled out, rebuilding the affected instance from a known-good state may be more appropriate than attempting to clean it in place.
  • Incorporate KEV monitoring into vulnerability management: Systems exposed to the internet should be routinely checked against CISA’s KEV Catalog so that confirmed exploitation is reflected in patching and investigation priorities.
How can we help you?
Help

How can we help you?

Subscribe: I'd like to keep in touch

If your enquiry is urgent please call +44 20 3321 7000

I'm a client

I'm looking for advice

Something else