> GitLab patches a max-severity regex flaw alongside five high-severity bugs

GitLab just fixed a max-severity vulnerability that could allow unauthenticated attackers to execute arbitrary code on its servers. The company released a fix on Monday, alongside patches for five other high-severity flaws affecting its source code management and continuous integration and delivery (CI/CD) platform. The vulnerability, tracked as CVE-2026-97229, was fixed in versions 19.4.2, 19.3.5, and 19.2.8 of its Community Edition (CE) and Enterprise Edition (EE), according to a patch advisory. The company urged administrators of self-managed installations running affected versions to upgrade immediately. GitLab.com is already running the patched version, while GitLab Dedicated customers do not need to take action, the company said in the advisory. The release also addresses vulnerabilities that could expose protected environment variables, allow unauthorized pipeline execution, and enable attackers to inject crafted content into AI agent instructions. The fixes span both CE and EE, with some issues affecting only the Enterprise Edition. “When no specific deployment type (omnibus, source code, Helm chart, etc.) of a product is mentioned, it means all types are affected,” GitLab added. Critical regex flaw could enable unauthenticated code execution GitLab described CVE-2026-97229 as an integer overflow issue in the platform’s CI/CD regular expression compiler. Under certain conditions, insufficient validation of regular expressions could have allowed an unauthenticated attacker to execute arbitrary code on the GitLab server by supplying a specially crafted regular expression in a CI/CD configuration. The vulnerability affects GitLab CE and EE versions from 19.2 before 19.2.8, 19.3 before 19.3.5, and 19.4 before 19.4.2. It carries a maximum CVSS score of 10.0 for potentially allowing remote code execution without authentication, with impacts on confidentiality, integrity, and availability across security boundaries. GitLab credited researcher Johan Carlsson with reporting the flaw through its HackerOne bug bounty program. Pipeline permissions and AI agents in the crosshairs Among the five high-severity vulnerabilities, CVE-2026-92883 could allow an authenticated user to execute arbitrary JavaScript in other users’ browser sessions through a specially crafted repository. The cross-site scripting flaw resulted from improper sanitization of HTML attributes in syntax-highlighted output and carries a CVSS score of 8.7. Two other flaws target pipeline security. CVE-2026-16301 (CVSS 8.5) could have allowed users with the Developer role to execute CI/CD pipelines on protected branches without authorization. CVE-2026-14814 (CVSS 8.2) potentially enabled attackers to poison cached responses for raw repository files, potentially causing targeted pipelines to execute malicious content and access protected environment variables. The remaining issues affect scheduled pipeline execution and GitLab Duo. CVE-2026-81839 (CVSS 7.7) could have allowed authenticated users to run arbitrary pipelines in a transferred project with the new group’s privileges. Another, CVE-2026-96893 (CVSS 7.3), could have allowed an authenticated user to inject crafted content into AI agent instructions, potentially causing unintended command execution attributed to other users. GitLab said it plans to make vulnerability issue details public 90 days after the release in which they were patched. Administrators should therefore prioritize the applicable security updates rather than wait for further technical disclosure. The release also fixes several low-to-medium severity vulnerabilities affecting GitLab Pages, Kubernetes proxying, GraphQL APIs, merge requests, custom roles, the package registry, and repository and project import functions.