GitLab has shipped a critical patch release for self-managed servers, and the headline fix carries the maximum CVSS score of 10.0. Tracked as CVE-2026-97229, the flaw is an integer overflow in the regular expression compiler used by GitLab CI/CD. GitLab says that under certain conditions it could have let an unauthenticated user execute arbitrary code on the GitLab server through a specially crafted regular expression in a CI/CD configuration.
Versions 19.4.2, 19.3.5 and 19.2.8 of GitLab Community Edition (CE) and Enterprise Edition (EE), released on October 12, 2026, close that hole along with 23 other security issues. In its release notes, GitLab strongly recommends that every self-managed installation upgrade immediately. GitLab.com is already running the patched code, and GitLab Dedicated customers do not need to take action. Hong Kong's computer emergency response team, HKCERT, relayed the advisory in a bulletin on October 13.
A regex in a pipeline file is the way in
Pipeline configuration is where teams tell GitLab what to build, test and deploy. According to GitLab, insufficient validation of the regular expressions in that configuration is what made the overflow reachable. The bug affects all versions from 19.2 before 19.2.8, 19.3 before 19.3.5, and 19.4 before 19.4.2.
GitLab credits the researcher known as joaxcar, who reported it through the company's HackerOne bug bounty program. GitLab has not said the flaw is being exploited, and under its standard policy the detailed issue stays private on its tracker for 90 days after the fix ships.
Five high-severity fixes ride along
- CVE-2026-92883 (CVSS 8.7): cross-site scripting in syntax-highlighted output, which could let an authenticated user run JavaScript in other users' browser sessions through a crafted repository. Reported by a0xnirudh.
- CVE-2026-16301 (CVSS 8.5): improper authorization in the downstream pipeline creation service, which could let a user with the Developer role run CI/CD pipelines on protected branches. Reported by sim4n6.
- CVE-2026-14814 (CVSS 8.2): a permissive regular expression in repository file access that could let a user poison cached raw-file responses, so targeted users' pipelines execute crafted content and potentially expose protected environment variables. Reported by ahacker1.
- CVE-2026-81839 (CVSS 7.7, EE only): improper cleanup of scheduled pipeline execution policy records, which could let a user run pipelines in a transferred project with the new group's privileges. Reported by no_01.
- CVE-2026-96893 (CVSS 7.3, EE only): a prompt injection issue in the GitLab Duo Agent Platform, where crafted content injected into AI agent instructions could cause unintended command execution attributed to other users. Found internally by GitLab's Mert Coskuner.
The remaining 18 fixes are rated medium (14) or low (4). Most are authorization bugs spread across GraphQL, work items, the package registry and fine-grained personal access tokens, alongside a server-side request forgery issue in repository import and a page cache poisoning bug in merge requests.
Upgrade to 19.4.2, 19.3.5 or 19.2.8 now
Administrators of self-managed instances should move to the latest patch release for their branch. GitLab says that when no deployment type is named, all of them (Omnibus packages, source installs and Helm charts) are affected. Servers on branches older than 19.2 fall outside this release train and need an upgrade to a supported version to receive the fixes.
This is not the first time this year a GitLab bug has demanded fast action. An unauthenticated file-read flaw landed on CISA's exploited list in September, and in August a GraphQL bug let outsiders delete public projects. A GitLab server typically holds source code, CI secrets and deployment credentials in one place, which is why a code execution bug that needs no login deserves a patch window measured in hours, not weeks.
This briefing is provided by IntelFusions for informational and defensive purposes only. It is based on sources assessed to be reliable at the time of writing, and analytic judgments carry the confidence levels indicated. Indicators of compromise are defanged; re-arm them only in controlled environments. IntelFusions is not affiliated with the organizations named and makes no warranty as to completeness or accuracy.