GitLab Community Edition and Enterprise Edition Integer Overflow or Wraparound Vulnerability
GitLab — Community Edition and Enterprise Edition
- Added to KEV catalog
- 29 October 2026
- Federal remediation due date
- 1 November 2026
- Weakness classification (CWE)
- CWE-190
AI Breakdown
What it is
GitLab Community Edition and Enterprise Edition contain an integer overflow vulnerability caused by insufficient regular expression validation. An unauthenticated attacker can exploit this weakness by submitting a specially crafted regular expression inside a CI/CD configuration. This allows remote attackers to execute arbitrary code directly on the GitLab server without requiring login credentials.
Why it matters
This vulnerability allows unauthorized attackers to gain complete control over critical development environments and code repositories. While specific use in ransomware campaigns is currently unknown, the flaw is confirmed to be actively exploited in the wild. Internet-exposed GitLab servers face immediate risk of compromise if left unaddressed.
Recommended action
IT teams must immediately apply the latest vendor patches and mitigations following vendor instructions and BOD 26-04 guidelines. Evaluate all GitLab assets to determine their internet exposure and conduct forensics triage as required by CISA. If mitigations cannot be implemented, organizations must isolate or discontinue use of the product.
AI-generated from CISA and NVD data — treat as a starting point, not a substitute for your own risk assessment.
CISA Description
GitLab Community Edition and Enterprise Edition contain a integer overflow or wraparound vulnerability that could allow 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.
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.
Notes
Other products can potentially be affected by the same underlying Ruby/Onigmo Integer Overflow issue in CI/CD Regular Expression Compiler. For more information please see: https://www.ruby-lang.org/en/news/2026/10/23/regexp-fixes-for-gitlab-cves ; https://docs.gitlab.com/releases/patches/patch-release-gitlab-19-4-2-released/ ; BOD 26-04: https://www.cisa.gov/news-events/directives/bod-26-04-prioritizing-security-updates-based-risk ; Forensics Triage Requirements: https://www.cisa.gov/news-events/directives/bod-26-04-implementation-guidance-prioritizing-security-updates-based-risk ; https://nvd.nist.gov/vuln/detail/CVE-2026-97229
More GitLab Vulnerabilities
GitLab Community Edition and Enterprise Edition Path Traversal Vulnerability
GitLab Server-Side Request Forgery (SSRF) Vulnerability
GitLab Community and Enterprise Editions Server-Side Request Forgery (SSRF) Vulnerability
GitLab Community and Enterprise Editions Improper Access Control Vulnerability
GitLab Community and Enterprise Editions Remote Code Execution Vulnerability
Is this vulnerability present in your environment?
CRS delivers independent VAPT assessments that identify exactly which known-exploited vulnerabilities exist in your network, applications, and infrastructure.
Explore VAPT Services







