At a glance
In the news, the most significant GitLab vulnerability tracked in our security news is CVE-2026-97229 (critical severity, CVSS score 10.0), actively exploited according to CISA.
As of November 1, 2026, 6 GitLab vulnerabilities are listed in CISA's catalog of vulnerabilities exploited by attackers, including 1 used in ransomware. The most recent, CVE-2026-97229, was added on October 29, 2026.
Among the GitLab vulnerabilities from the last four months in the NVD, the most severe is CVE-2026-110264 (score 10.0), published on October 22, 2026.
Are you affected? Help menu (?) → About GitLab, or /help on your instance, shows the version to compare with the latest security release.
Actively exploited
GitLab vulnerabilities exploited by attackers
CISA's Known Exploited Vulnerabilities (KEV) catalog only lists vulnerabilities whose real-world exploitation has been confirmed. These are the first ones to patch.
| CVE | Product | Date added | Ransomware |
|---|---|---|---|
| CVE-2026-97229 GitLab Community Edition and Enterprise Edition Integer Overflow or Wraparound Vulnerability. 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. | Community Edition and Enterprise Edition | October 29, 2026 | Not reported |
| CVE-2026-85706 GitLab Community Edition and Enterprise Edition Path Traversal Vulnerability. GitLab Community Edition and Enterprise Edition contains a path traversal vulnerability that allows an unauthenticated user to read arbitrary files due to an improper path confinement and missing authentication enforcement in the repository commits API. | Community Edition and Enterprise Edition | September 11, 2026 | Not reported |
| CVE-2021-22175 GitLab Server-Side Request Forgery (SSRF) Vulnerability. GitLab contains a server-side request forgery (SSRF) vulnerability when requests to the internal network for webhooks are enabled. | GitLab | February 18, 2026 | Not reported |
| CVE-2021-39935 GitLab Community and Enterprise Editions Server-Side Request Forgery (SSRF) Vulnerability. GitLab Community and Enterprise Editions contain a server-side request forgery vulnerability which could allow unauthorized external users to perform Server Side Requests via the CI Lint API. | Community and Enterprise Editions | February 3, 2026 | Not reported |
| CVE-2023-7028 GitLab Community and Enterprise Editions Improper Access Control Vulnerability. GitLab Community and Enterprise Editions contain an improper access control vulnerability. This allows an attacker to trigger password reset emails to be sent to an unverified email address to ultimately facilitate an account takeover. | GitLab CE/EE | May 1, 2024 | Not reported |
| CVE-2021-22205 GitLab Community and Enterprise Editions Remote Code Execution Vulnerability. GitHub Community and Enterprise Editions that utilize the ability to upload images through GitLab Workhorse are vulnerable to remote code execution. Workhorse passes image file extensions through ExifTool, which improperly validates the image files. | Community and Enterprise Editions | November 3, 2021 | Yes |
New CVEs
GitLab vulnerabilities from the last four months
- CVE-2026-110264published October 22, 2026An issue has been discovered in GitLab CE/EE affecting all versions from 7.0 before 18.11.13, 19.0 before 19.0.10, 19.1 before 19.1.9, 19.2 before 19.2.9, 19.3 before 19.3.6, 19.4 before 19.4.3, and 19.5 before 19.5.1 that, under certain conditions, could have allowed an unauthenticated user to execute arbitrary code on the GitLab server due to integer overflow when compiling a specially crafted regular expression.Critical10.0
- CVE-2026-85706published September 12, 2026GitLab has remediated an issue in GitLab CE/EE affecting all versions from 18.7 before 18.11.12, 19.0 before 19.0.9, 19.1 before 19.1.8, 19.2 before 19.2.6, and 19.3 before 19.3.2 that, under certain conditions, an unauthenticated user could have read arbitrary files from the GitLab server due to improper path confinement and missing authentication enforcement in the repository commits API.Critical10.0
- CVE-2026-102649published October 26, 2026Burrito is a Terraform Automation Collaboration Software (TACoS) Kubernetes operator. Prior to 0.13.0, `POST /api/webhook` accepts unsigned GitHub and GitLab events when a `TerraformRepository`'s credentials omit `webhookSecret` or set it to an empty value, including credentials configured for git authentication and polling. `Credential.WebhookSecret` is optional, and `go-playground/webhooks` skips signature or token verification when the secret is empty. Anyone who can reach `burrito-server`'s endpoint and knows a tracked repository's URL can forge events to create or delete `TerraformPullRequest` custom resources with attacker-chosen `Branch`, `Base`, and `ID` fields. For GitHub `pull_request` events, the controller fetches changed files using the real pull request number but does not cross-check the payload's branch against that pull request. Pairing a real, existing pull request number with an unrelated existing branch in the same repository can therefore cause an unauthorized `terraform plan` for affected layers using the operator's stored git and cloud credentials. Code analysis also indicates that the resulting plan can be posted to the real pull request's comment thread, exposing and misattributing another branch's infrastructure changes. Auto-apply is disabled for these temporary layers, so this vulnerability alone cannot force a `terraform apply`; plan-time provider and data-source code execution depends on the selected branch's contents. This issue is fixed in version 0.13.0.Critical9.9
- CVE-2026-90970published October 2, 2026GitLab has remediated a vulnerability in the GitLab AI Gateway component affecting all versions of the AI Gateway from 18.1.6 before 19.2.4, 19.3 before 19.3.2, and 19.4 before 19.4.1 that, under certain conditions, could have allowed an authenticated user with Duo Agent Platform access to escape the prompt template sandbox via a specially crafted flow configuration, resulting in arbitrary command execution on the AI Gateway.Critical9.9
- CVE-2026-93577published September 24, 2026GitLab has remediated an issue in GitLab CE/EE affecting all versions from 19.2 before 19.2.7, 19.3 before 19.3.3, and 19.4 before 19.4.1 that under certain conditions could have allowed an authenticated user to execute arbitrary code on the GitLab server due to an integer overflow issue when compiling a specially crafted regular expression in a CI/CD configuration.Critical9.9
- CVE-2026-89078published September 24, 2026GitLab has remediated an issue in GitLab CE/EE affecting all versions from 19.2 before 19.2.7, 19.3 before 19.3.3, and 19.4 before 19.4.1 that under certain conditions could have allowed an authenticated user to execute arbitrary code on the GitLab server due to a double free issue when parsing a specially crafted regular expression in a CI/CD configuration.Critical9.9
- CVE-2026-87719published September 12, 2026GitLab has remediated an issue in GitLab EE affecting all versions from 18.3 before 18.11.12, 19.0 before 19.0.9, 19.1 before 19.1.8, 19.2 before 19.2.6, and 19.3 before 19.3.2 that under certain conditions could allow an authenticated user with Duo Chat access to obtain Advanced Search instance configurations and sensitive credentials using a specially crafted GraphQL subscription argument to bypass serialization and perform server object lookup.Critical9.9
- CVE-2026-72867published August 10, 2026Dokploy is a free, self-hostable Platform as a Service (PaaS). From 0.29.3 until 0.29.13, the incomplete fix for CVE-2026-45628 leaves packages/server/src/db/schema/compose.ts branch fields without server-side validation, allowing a direct compose.update request to store a malicious customGitBranch, branch, gitlabBranch, bitbucketBranch, or giteaBranch. A low-privileged authenticated user can trigger compose.deploy, which passes the stored branch to shell-based Git clone commands in packages/server/src/utils/providers/git.ts, github.ts, gitlab.ts, bitbucket.ts, and gitea.ts, resulting in arbitrary host command execution. This issue is fixed in version 0.29.13.Critical9.9
- CVE-2026-61560published September 16, 2026`@zereight/mcp-gitlab` is a Model Context Protocol server for GitLab. Prior to version 2.1.27, the SSE transport mode (`SSE=true`) exposes all MCP tools without any authentication. The `upload_markdown` tool reads arbitrary files from the server's local filesystem via an unsanitized `file_path` parameter and uploads them to a GitLab project. Combined, any unauthenticated network-reachable attacker can read `/proc/self/environ` to steal the server's `GITLAB_PERSONAL_ACCESS_TOKEN` and achieve full GitLab account takeover. This is the default configuration for Docker deployments. Version 2.1.27 contains a patch.Critical9.8
- CVE-2026-86059published September 22, 2026Dokploy is a free, self-hostable Platform as a Service (PaaS). Prior to 0.29.13, Dokploy organization members without Git provider access can retrieve plaintext provider credentials through github.one, gitlab.one, gitea.one, and bitbucket.one because those protected procedures return full provider rows without applying getAccessibleGitProviderIds or an organization check. The application.one route also returns nested GitHub, GitLab, Gitea, and Bitbucket relations from findApplicationById with GitHub App private keys, OAuth tokens, client secrets, webhook secrets, and app passwords even when hasGitProviderAccess is false. A member with application read access or a provider identifier can therefore bypass per-member provider assignment and use the exposed credentials to access private repositories or manipulate external workflows. This issue is fixed in version 0.29.13.Critical9.6
- CVE-2026-61568published September 15, 2026`@zereight/mcp-gitlab` is a Model Context Protocol server for GitLab. Versions prior to 2.1.30 expose the Streamable HTTP MCP endpoint without an effective Host or Origin allowlist. A malicious web page can use DNS rebinding to route browser requests to a victim's local MCP listener while preserving an attacker-controlled `Host` and `Origin`. The server accepts those headers and reaches the MCP initialization path instead of rejecting the request at the HTTP boundary. Version 2.1.30 contains a patch.Critical9.6
- CVE-2026-19478published August 17, 2026GitLab has remediated an issue in GitLab CE/EE affecting all versions from 18.2 before 18.11.11, 19.0 before 19.0.8, 19.1 before 19.1.6, and 19.2 before 19.2.4 that under certain conditions could allow an unauthenticated user to remotely modify or delete public projects and user data via a GraphQL directive.Critical9.4
In our security news
Recent GitLab vulnerabilities
| CVE | Severity | Exploited (CISA) | Published |
|---|---|---|---|
| CVE-2026-97229 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. | Critical10.0 | Yes, since October 29, 2026 | October 13, 2026 |
Sources: NIST's National Vulnerability Database (NVD) for the CVSS score, CISA's Known Exploited Vulnerabilities (KEV) catalog for active exploitation. Official descriptions in their original wording.
Security news
GitLab news
- November 1, 2026Alpine Linux reconstruit son instance GitLab après une tentative d'attaque par exécution de code à distanceBleepingComputer ↗
- October 30, 2026CISA alerte sur l'exploitation en milieu réel d'une faille critique de GitLab corrigée il y a peuBleepingComputer ↗
- October 30, 2026CISA intègre deux vulnérabilités exploitées activement (GitLab et Cisco) dans sa liste KEVCVE-2026-97229The Hacker News ↗
- October 23, 2026Ruby corrige trois failles dans son moteur d'expressions régulières responsables de quatre vulnérabilités RCE critiques dans GitLabThe Hacker News ↗
A GitLab vulnerability in your environment?
Patching a known CVE is not enough: our AI agents actually attack your applications and hand you proof of every open door.
