CVE-2026-97229: Integer Overflow or Wraparound in GitLab
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.
Other sources
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.
— NVD
Integer Overflow or Wraparound in GitLab
— Microsoft
Affected Software
Remediation
Recommended actions to resolve this vulnerability, in priority order.
- Upgrade
Upgrade
azurelinux/rubyto a version that resolves this vulnerability.Fixed in 3.3.13-0 - Upgrade
Upgrade
azurelinux/rubyto a version that resolves this vulnerability.Fixed in 0:3.4.12-38.azl4 - Upgrade
Upgrade
bitnami/gitlabto a version that resolves this vulnerability.Fixed in 19.2.8 - Upgrade
Upgrade
bitnami/gitlabto a version that resolves this vulnerability.Fixed in 19.3.5 - Upgrade
Upgrade
bitnami/gitlabto a version that resolves this vulnerability.Fixed in 19.4.2 - Upgrade
Upgrade
alpine/rubyto a version that resolves this vulnerability.Fixed in 3.3.13-r0 - Upgrade
Upgrade
alpine/rubyto a version that resolves this vulnerability.Fixed in 3.4.12-r0 - Upgrade
Upgrade
GitLab Community Edition and Enterprise Editionto a version that resolves this vulnerability.Fixed in 19.2.8 - Upgrade
Upgrade
GitLab Community Edition and Enterprise Editionto a version that resolves this vulnerability.Fixed in 19.3.5 - Upgrade
Upgrade
GitLab Community Edition and Enterprise Editionto a version that resolves this vulnerability.Fixed in 19.4.2
Event History
Frequently Asked Questions
Which GitLab versions need remediation?
GitLab CE/EE versions 19.2 before 19.2.8, 19.3 before 19.3.5, and 19.4 before 19.4.2 are affected. Upgrade to 19.2.8, 19.3.5, 19.4.2, or a later version in the applicable release line.
Does exploitation require an authenticated GitLab account or user interaction?
No. The issue could allow an unauthenticated user to execute arbitrary code on the GitLab server, and the provided vector indicates no user interaction is required.
What input is involved in exploitation?
Exploitation involves a specially crafted regular expression in a CI/CD configuration. The issue is attributed to insufficient regular-expression validation under certain conditions.