VYPR
Vypr IntelligenceAI-generatedOct 13, 2026· 18 CVEs

GitLab: 18 Vulnerabilities Disclosed, Critical RCE Flaw Exploitable

GitLab disclosed 18 vulnerabilities in CE/EE, including a critical RCE flaw (CVE-2026-97229) with a public exploit, necessitating urgent patching.

Key findings

  • 18 GitLab CE/EE vulnerabilities disclosed on October 13, 2026, patched in versions 19.2.8, 19.3.5, 19.4.2.
  • Critical CVE-2026-97229 (CVSS 10.0) allows unauthenticated RCE via crafted regex in CI/CD configs; public PoC exists.
  • Multiple authorization flaws permit unauthenticated/authenticated users to access sensitive data or perform unauthorized actions.
  • Vulnerabilities impact CI/CD pipelines, project imports, repository data, and internal network access.
  • Urgent patching recommended for all self-managed GitLab instances due to the severity and exploitability of CVE-2026-97229.

On October 13, 2026, GitLab disclosed a significant batch of 18 vulnerabilities affecting both GitLab Community Edition (CE) and Enterprise Edition (EE). The vulnerabilities, patched across multiple versions, range in severity from low to critical, with one critical flaw (CVE-2026-97229) allowing for unauthenticated remote code execution. This coordinated disclosure highlights a broad range of security weaknesses within the platform, impacting various components and functionalities.

A critical remote code execution vulnerability, CVE-2026-97229, stands out due to its CVSS score of 10.0. This flaw stems from an integer overflow in the CI/CD regular expression compiler. Under specific conditions, an unauthenticated user could exploit this by submitting a specially crafted regular expression in a CI/CD configuration, leading to arbitrary code execution on the GitLab server. Publicly available proof-of-concept exploits for this vulnerability have been released, increasing the urgency for users to patch. Cyber Security News

Several other vulnerabilities focus on authorization bypasses and information disclosure. CVE-2026-85529 and CVE-2026-16275, both medium-severity, could allow unauthenticated users to read internal or confidential notes on public projects due to improper authorization checks. Similarly, CVE-2026-84284, also medium-severity, permitted unauthenticated users to access work item contents from private groups. Authenticated users also faced risks, with CVE-2026-78335 and CVE-2026-14210 allowing authenticated users with specific token scopes to modify group integrations or delete/modify group-level labels, respectively.

Further impacting authenticated users, CVE-2026-92883, a high-severity vulnerability, could enable the execution of arbitrary JavaScript in other users' browser sessions via a crafted repository. CVE-2026-101168, a medium-severity flaw, could expose sensitive authentication tokens from GitLab Pages log data to authenticated users with access to those logs. Another medium-severity issue, CVE-2026-6567, allowed authenticated users with reporter roles to access restricted CI artifact report content.

The batch also includes vulnerabilities related to CI/CD pipelines and project imports. CVE-2026-103549, a low-severity flaw, allowed authenticated users with specific permissions to import projects. CVE-2026-16301, a high-severity vulnerability, enabled authenticated developers to execute CI/CD pipelines on protected branches without proper authorization. CVE-2026-14814, a high-severity flaw, allowed users to poison cached responses for raw repository files, potentially leading to the execution of malicious content in CI/CD pipelines. CVE-2026-7767, a medium-severity vulnerability, could allow an authenticated user controlling a Kubernetes agent to send sensitive authentication tokens to unintended servers.

Several lower-severity issues were also addressed. CVE-2026-5954, a medium-severity vulnerability, allowed users to download package files from public projects. CVE-2026-14552, medium-severity, permitted authenticated users with guest access to read confidential epic content. CVE-2026-100755, a medium-severity flaw, could allow authenticated users to poison cached page content. Finally, CVE-2026-100104, a low-severity vulnerability, enabled authenticated users to perform server-side request forgery and access internal network resources.

GitLab addressed these vulnerabilities in patch releases 19.2.8, 19.3.5, and 19.4.2. The company strongly recommends that all self-managed GitLab installations be upgraded immediately. GitLab.com and GitLab Dedicated tenants have already been patched. The coordinated disclosure of these 18 vulnerabilities underscores the importance of timely patching and continuous security monitoring for GitLab users, especially given the existence of public exploits for the critical RCE flaw. GitLab Security Releases

AI-written article. Grounded in 18 CVE records listed below.