Black Friday60% off BLACKFRIDAY2026
PlatformPlansPartners
Resources
ToolsBlogDocs
Sign Up →
critical·Product Based Web Vulnerabilities·Updated Nov 9, 2026

CVE-2026-97229 Scanner

CVE-2026-97229 Scanner - Remote Code Execution (RCE) vulnerability in GitLab CE/EE

Est. Time~10 seconds
Scan TypeSingle Scan
Targetsdomain, subdomain, ipv4
CostFree
3
Times Used
continuous scan runs
4.2k
Continuously Checked
assets under CS
0
Vulnerabilities Found
confirmed findings
References
🔴
CISA Known Exploited Vulnerability
This CVE is actively exploited in the wild. CISA mandates federal agencies to patch immediately.
10.0
CVSScritical
Exploitable remotely over the internet · no authentication required.
Description

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.

Attack Vector
Network
Privileges Req.
None
User Interaction
None
Affected
GitLabby GitLab
AFFECTED< 19.2.8→SAFE ✓≥ 19.2.8
Updated Nov 6, 2026View on NVD →
Detail

GitLab CE/EE is a widely used software development platform that provides a web-based interface for Git repositories. It is utilized by development teams across various industries to manage source code, track issues, and conduct code reviews, among other tasks. GitLab facilitates collaborative software development by offering continuous integration and continuous deployment (CI/CD) capabilities, which allow teams to automate testing and deployment processes. The software is available as both a self-hosted solution and a cloud-hosted service, accommodating diverse user preferences and deployment needs. GitLab's extensive integration options and API support increase its adoption among enterprises aiming to streamline their DevOps workflows. The product's varying editions cater to different user requirements, from small teams to large enterprises with complex compliance needs.

The identified vulnerability in GitLab CE/EE involves remote code execution (RCE) through an Onigmo Integer Overflow. This RCE vulnerability arises from insufficient regular expression validation within CI/CD configuration files, allowing attackers to execute arbitrary code. An exploit leveraging this weakness can be carried out by an unauthenticated user, posing a significant threat to systems running vulnerable GitLab versions. This flaw could potentially enable full system compromise, as it permits the execution of hostile scripts by remote attackers. It underscores the importance of prompt updates and configurations to safeguard against unauthorized access. Due to the critical nature of this vulnerability, rapid remediation is advised to prevent exploitation.

The vulnerability specifically impacts versions of GitLab CE/EE prior to 19.2.8, 19.3.5, and 19.4.2. It exists in the CI/CD configuration processing, where crafted regular expressions can bypass validation checks. This vulnerability can be exploited via the GitLab CI/CD API endpoint, where malicious inputs initiate and execute unauthorized code on the server. Key technical aspects include inadequate boundaries for regular expression processing, culminating in potential integer overflow conditions. Attackers exploit this by injecting specially crafted expressions that the server misinterprets, leading to the execution of arbitrary commands. Given GitLab's extensive usage, this vulnerability represents a considerable security concern for affected deployments.

Exploiting this vulnerability can lead to severe consequences, such as unauthorized command execution, data leakage, and potential system takeover. Malicious actors can compromise sensitive data, escalate privileges, or disrupt service availability. This can correspondingly result in financial losses, reputational damage, or regulatory consequences for affected organizations. Additionally, disrupted CI/CD pipelines could hinder development processes, delaying product releases and impacting business operations. The critical nature of this flaw necessitates immediate attention to prevent such adverse effects through timely system updates and security assessments.

REFERENCES

Solution Advice
  • Upgrade GitLab CE/EE to versions 19.2.8, 19.3.5, 19.4.2, or later.
  • Regularly monitor and apply security patches as released by GitLab.
  • Restrict API access to trusted users and networks only.
  • Implement web application firewalls (WAF) to detect and block malicious payloads.
  • Conduct thorough security assessments of the CI/CD configurations to identify vulnerabilities.

Get AI-powered remediation steps tailored to your asset.

Try AI Solutions →

Check your infrastructure.
Right now.

12,000+ scanners. Free to start. No credit card required.