CVE-2026-97229

CRITICAL(10.0)KEVLikely Exploited

GitLab Community Edition and Enterprise Edition Integer Overflow or Wraparound Vulnerability

Description

CVE-2026-97229 is a critical remote code execution vulnerability in GitLab Community Edition and Enterprise Edition that, under certain conditions, allows an unauthenticated attacker to execute arbitrary code on the GitLab server. The flaw is triggered by a specially crafted regular expression in a CI/CD configuration and stems from insufficient regular expression validation, with the underlying weakness classified as an integer overflow or wraparound. GitLab versions 19.2 before 19.2.8, 19.3 before 19.3.5 and 19.4 before 19.4.2 are affected, and a successful exploit gives the attacker control over the server that hosts source code, pipelines and their secrets. CISA has added CVE-2026-97229 to its Known Exploited Vulnerabilities (KEV) catalog, and its EPSS score of 27.3% ranks it in the top 2% of all scored vulnerabilities.

KEV Information

Vendor
GitLab
Product
Community Edition and Enterprise Edition
Date Added
October 29, 2026
Due Date
November 1, 2026
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.

CVSS Score

Vector String
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:H/A:HOpen in Calculator
Attack Vector
NETWORK
Attack Complexity
LOW
Privileges Required
NONE
User Interaction
NONE
Scope
CHANGED
Confidentiality Impact
HIGH
Integrity Impact
HIGH
Availability Impact
HIGH
Exploitability Score
3.9
Impact Score
6.0

CWEs

Affected Products

VendorProductVersion
gitlabgitlab>= 19.2.0, < 19.2.8; >= 19.3.0, < 19.3.5; >= 19.4.0, < 19.4.2
ruby-langruby>= 3.3.0, < 3.3.13; >= 3.4.0, < 3.4.12; >= 4.0.0, < 4.0.8

References

Weakness Type

CWE-190: Integer Overflow or Wraparound

An integer overflow occurs when an arithmetic operation produces a value larger than the target integer type can hold, so the value wraps around to a small or negative number and can bypass size checks. In GitLab CE/EE, a specially crafted regular expression in a CI/CD configuration that is not sufficiently validated can reach this condition and lead to arbitrary code execution on the server.

Learn more: CWE-190 — Integer Overflow or Wraparound

Impact Analysis

CVE-2026-97229 has the maximum CVSS 3.1 base score of 10.0 (CRITICAL). It is remotely exploitable over the network, easy to exploit with no special conditions, requires no authentication and no user action. The scope is changed, so the impact reaches beyond the vulnerable component to the GitLab server itself. Confidentiality (High), Integrity (High) and Availability (High) are all fully affected: an attacker who executes code on the server can read repositories and CI/CD secrets, tamper with source code and pipelines, and disrupt the service. Given the confirmed exploitation in the KEV catalog and an EPSS score in the 98th percentile, exposed GitLab instances face an immediate risk; ransomware usage is listed as unknown.

Exploit Maturity

CISA lists CVE-2026-97229 in its KEV catalog, which confirms active exploitation in the wild against GitLab CE/EE. The references include a pull request to the Rapid7 Metasploit Framework, indicating that exploit tooling for this vulnerability is being integrated into a widely used penetration testing framework, as well as a Ruby announcement on regexp fixes for GitLab CVEs. With an EPSS score of 27.3% (98th percentile), the probability of exploitation is far higher than for almost all other vulnerabilities. Affected instances should be treated as potentially compromised and patched immediately.

Remediation

  1. Follow the CISA KEV required action: "Apply mitigations in accordance with vendor instructions, ensuring compliance with CISA's BOD 26-04 Prioritizing Security Updates Based on Risk guidance and CISA's 'Forensics Triage Requirements'." Discontinue use of the product if mitigations are unavailable. The KEV due date was 2026-11-01.
  2. Upgrade GitLab CE/EE to 19.2.8, 19.3.5 or 19.4.2 or later, as described in the GitLab patch release notes. All releases from 19.2.0 up to these versions are affected.
  3. Until the update is installed, restrict network access to the GitLab instance (for example to VPN or internal networks only) and review who can submit or modify CI/CD configurations.
  4. Hunt for signs of compromise: review CI/CD configuration changes for unusual regular expressions, check server logs and processes for unexpected command execution, and follow CISA's forensic triage requirements. Rotate CI/CD variables, tokens and other secrets stored on the instance if compromise cannot be ruled out.
  5. In the long term, keep GitLab on the current patch release and treat integer overflow risks in input processing seriously; validating that arithmetic operations cannot overflow and checking against type limits are the core defenses for this weakness class.

Technical Details

CVE-2026-97229 maps to CWE-190, where an arithmetic operation exceeds the maximum value of its integer type and wraps around to a small or negative number, which can bypass size checks and cause undersized buffer allocations that are later overflowed. In GitLab CE/EE, the attack input is a specially crafted regular expression in a CI/CD configuration that is not sufficiently validated before processing; the related Ruby announcement on regexp fixes for GitLab CVEs points to the regular expression handling as the affected area. The CVSS vector CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:H/A:H describes a network attack (AV:N) with low complexity (AC:L) that needs neither privileges (PR:N) nor user interaction (UI:N). Because successful exploitation results in arbitrary code execution on the GitLab server, the impact crosses the component boundary (S:C) with full loss of confidentiality, integrity and availability.

Frequently Asked Questions

Is CVE-2026-97229 being actively exploited?

Yes. CISA has added CVE-2026-97229 to its Known Exploited Vulnerabilities catalog, confirming exploitation in the wild, with a remediation due date of 2026-11-01. The EPSS score of 27.3% places it in the 98th percentile, and ransomware usage is listed as unknown.

What products are affected by CVE-2026-97229?

GitLab Community Edition and Enterprise Edition are affected in versions 19.2.0 before 19.2.8, 19.3.0 before 19.3.5 and 19.4.0 before 19.4.2. The fixed releases are 19.2.8, 19.3.5 and 19.4.2.

How do I fix CVE-2026-97229?

Upgrade GitLab CE/EE to 19.2.8, 19.3.5, 19.4.2 or later and follow CISA's KEV required action, including BOD 26-04 and the forensic triage requirements. Until patched, restrict access to the instance, review CI/CD configurations and rotate secrets if compromise is suspected.

How severe is CVE-2026-97229?

CVE-2026-97229 is rated CRITICAL with the maximum CVSS 3.1 score of 10.0, because an unauthenticated remote attacker can execute arbitrary code on the GitLab server. Its EPSS score of 27.3% ranks it in the 98th percentile, and confirmed exploitation via the KEV catalog makes it a top priority.

CVSS Score

10.0
CRITICAL(10.0)

EPSS Score

EPSS Score69.29%
EPSS Percentile99.4%

Dates

PublishedOctober 13, 2026
Last ModifiedNovember 2, 2026
StatusAnalyzed
CVSS Versionv3.1

Need Help With Vulnerability Management?

Our security experts can help you prioritize and remediate vulnerabilities effectively.