GitLab GitLab Version Control Server
Don't miss out!
Thousands of developers use stack.watch to stay informed.Get an email whenever new security vulnerabilities are reported in any GitLab product.
RSS Feeds for GitLab security vulnerabilities
Create a CVE RSS feed including security vulnerabilities found in GitLab products with stack.watch. Just hit watch, then grab your custom RSS feed url.
Products by GitLab Sorted by Most Security Vulnerabilities since 2018
Known Exploited GitLab Vulnerabilities
The following GitLab vulnerabilities have been marked by CISA as Known to be Exploited by threat actors.
| Title | Description | Added |
|---|---|---|
| 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. CVE-2026-97229 Exploit Probability: 69.3% |
October 29, 2026 |
| 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. CVE-2026-85706 Exploit Probability: 97.4% |
September 11, 2026 |
| 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. CVE-2021-22175 Exploit Probability: 53.4% |
February 18, 2026 |
| 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. CVE-2021-39935 Exploit Probability: 36.1% |
February 3, 2026 |
| 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. CVE-2023-7028 Exploit Probability: 94.5% |
May 1, 2024 |
Of the known exploited vulnerabilities above, 4 are in the top 1%, or the 99th percentile of the EPSS exploit probability rankings. The vulnerability CVE-2021-39935: GitLab Community and Enterprise Editions Server-Side Request Forgery (SSRF) Vulnerability is in the top 5% of the currently known exploitable vulnerabilities.
By the Year
In 2026 there have been 254 vulnerabilities in GitLab with an average score of 5.8 out of ten. Last year, in 2025 GitLab had 162 security vulnerabilities published. That is, 92 more vulnerabilities have already been reported in 2026 as compared to last year. Last year, the average CVE base score was greater by 0.27
| Year | Vulnerabilities | Average Score |
|---|---|---|
| 2026 | 254 | 5.80 |
| 2025 | 162 | 6.07 |
| 2024 | 147 | 6.35 |
| 2023 | 183 | 5.61 |
| 2022 | 152 | 5.75 |
| 2021 | 157 | 5.44 |
| 2020 | 237 | 6.15 |
| 2019 | 165 | 6.33 |
| 2018 | 33 | 6.71 |
It may take a day or so for new GitLab vulnerabilities to show up in the stats or in the list of recent security vulnerabilities. Additionally vulnerabilities may be tagged under a different product or component name.
Recent GitLab Security Vulnerabilities
| CVE | Date | Vulnerability | Products |
|---|---|---|---|
| CVE-2026-12664 | Oct 21, 2026 |
GitLab Read-API Escalation via GraphQL Field before 19.3.6/19.4.3/19.5.1GitLab has remediated an issue in GitLab CE/EE affecting all versions from 18.2 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 authenticated user with a read_api-scoped token to retrieve a project's incoming email address and create work items, bypassing the token's restrictions, due to insufficient scope enforcement on a GraphQL field. |
|
| CVE-2026-13319 | Oct 21, 2026 |
GitLab CE/EE 15.10-19.5 Milestone API Auth Metadata LeakGitLab has remediated an issue in GitLab CE/EE affecting all versions from 15.10 before 19.3.6, 19.4 before 19.4.3, and 19.5 before 19.5.1 that, could have allowed an authenticated to read milestone metadata, including titles, descriptions, and full project paths, from arbitrary private projects across the instance without any project membership, due to missing authorization checks on a user-supplied project filter parameter in the group milestones API. |
|
| CVE-2026-14288 | Oct 21, 2026 |
GitLab EE Auth Bypass MR Approval Policy 17.4-19.5GitLab has remediated an issue in GitLab EE affecting all versions from 17.4 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 authenticated to bypass a required merge request approval policy on a protected branch due to improper access control during approval rule synchronization. |
|
| CVE-2026-15723 | Oct 21, 2026 |
GitLab CE/EE LDAP Takeover via OmniAuth SAML/LDAP Auto-linking (19.5.1)GitLab has remediated an issue in GitLab CE/EE affecting all versions from 10.1 before 19.3.6, 19.4 before 19.4.3, and 19.5 before 19.5.1 that, when OmniAuth SAML and LDAP auto-linking were both enabled, an authenticated user could have taken over an existing LDAP-backed account without any interaction from the targeted user, due to improper input sanitization in the LDAP email lookup path used during OmniAuth identity linking. |
|
| CVE-2026-16255 | Oct 21, 2026 |
GitLab EE Membership Lock Bypass (v <19.3.6/19.4.3/19.5.1)GitLab has remediated an issue in GitLab EE affecting all versions from 12.0 before 19.3.6, 19.4 before 19.4.3, and 19.5 before 19.5.1 that, when the instance-wide SAML or LDAP membership lock was enabled, an authenticated user could have granted or accepted project and group membership outside the identity provider's control, due to incomplete enforcement of the membership lock on requests created before the lock was enabled. |
|
| CVE-2026-103515 | Oct 21, 2026 |
GitLab EE <19.3.6, <19.4.3, <19.5.1 Duo lock bypass for AIegressGitLab has remediated an issue in GitLab EE affecting all versions from 19.2 before 19.3.6, 19.4 before 19.4.3, and 19.5 before 19.5.1 that, when an instance administrator locked a group's Duo availability, an authenticated user with group Owner permissions could have re-enabled AI-backed data egress to a third-party service for that group and its descendant projects, due to insufficient granularity of the admin-lock enforcement controls. |
|
| CVE-2026-105711 | Oct 21, 2026 |
GitLab CE/EE before 19.5.1 Fragment Cache Leak of Confidential Issue TitlesGitLab has remediated an issue in GitLab CE/EE affecting all versions from 15.0 before 19.3.6, 19.4 before 19.4.3, and 19.5 before 19.5.1 that, when a merge request in a public project referenced a confidential issue from a private project, an authenticated user with no project membership could have read the confidential issue's title, due to a viewer-independent fragment cache key that incorrectly shared per-user-redacted rendered content across all users. |
|
| CVE-2026-105777 | Oct 21, 2026 |
GitLab CE/EE <19.3.6, <19.4.3, <19.5.1 Unauth Internal Header LeakGitLab has remediated an issue in GitLab CE/EE affecting all versions from 17.6.5 before 19.3.6, 19.4 before 19.4.3, and 19.5 before 19.5.1 that, under certain conditions, an unauthenticated user could have retrieved sensitive internal server credentials due to improper filtering of internal response headers. |
|
| CVE-2026-112378 | Oct 21, 2026 |
GitLab EE <19.5.1 Auth Bypass of Paid AI via Billing CheckGitLab has remediated an issue in GitLab EE affecting all versions from 17.8 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 authenticated user to access paid AI features without a valid subscription due to insufficient server-side validation in billing eligibility checks. |
|
| CVE-2026-112212 | Oct 21, 2026 |
GitLab CE/EE OAuth/OIDC Cache Poison pre-19.5.1GitLab has remediated an issue in GitLab CE/EE affecting all versions from 18.3 before 19.3.6, 19.4 before 19.4.3, and 19.5 before 19.5.1 that, under certain conditions, an unauthenticated user could have poisoned a shared cache's OAuth/OIDC discovery document to redirect certain flows to an externally controlled server, due to improper trust of user-supplied values when constructing endpoint URLs in cached discovery responses. |
|
| CVE-2026-112326 | Oct 21, 2026 |
GitLab EE <19.3.6, <19.4.3, <19.5.1 AuthBypass Deletion of Vulnerability RecordsGitLab has remediated an issue in GitLab EE affecting all versions from 17.8 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 authenticated user with read-only permissions to permanently delete existing vulnerability records due to improper cleanup logic that failed to distinguish between pre-existing records from newly created ones during error handling. |
|
| CVE-2026-5954 | Oct 13, 2026 |
GitLab CE/EE Improper Auth Download Vulnerability (v15.119.4.2)GitLab has remediated an issue in GitLab CE/EE affecting all versions from 15.1 before 19.2.8, 19.3 before 19.3.5, and 19.4 before 19.4.2 that, under certain conditions, could have allowed a user to download package files from a public project due to improper authorization checks. |
|
| CVE-2026-6567 | Oct 13, 2026 |
Auth Reporter CI Artifact Access in GitLab CE/EE <19.2.8, 19.3.5, 19.4.2GitLab has remediated an issue in GitLab CE/EE affecting all versions from 13.8 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 authenticated user with reporter role to access restricted CI artifact report content they were not authorized to, due to missing authorization checks. |
|
| CVE-2026-7767 | Oct 13, 2026 |
GitLab CE/EE Kubernetes Proxy Redirect Validation Flaw (<=19.4.1)GitLab has remediated an issue in GitLab CE/EE affecting all versions from 13.11 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 authenticated user controlling a Kubernetes agent to cause sensitive authentication tokens to be sent to an unintended server due to improper redirect validation in the Kubernetes proxy. |
|
| CVE-2026-9268 | Oct 13, 2026 |
GitLab EE: Auth Bypass in CI/CD Rollback Settings v13.619.2.8, 19.3, 19.4GitLab has remediated an issue in GitLab EE affecting all versions from 13.6 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 authenticated user with limited permissions to modify project CI/CD deployment rollback settings without proper authorization, due to insufficient access control checks. |
|
| CVE-2026-14210 | Oct 13, 2026 |
GitLab CE/EE Auth Bypass: Delete/Modify Group Labels (18.11-19.4)GitLab has remediated an issue in GitLab CE/EE affecting all versions from 18.11 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 authenticated user with a project-scoped fine-grained Personal Access Token to permanently delete or modify group-level labels, due to incorrect authorization logic on label ownership scope validation. |
|
| CVE-2026-14552 | Oct 13, 2026 |
GitLab CE/EE Auth Bypass in Epic Content (v17.0-19.4.2)GitLab has remediated an issue in GitLab CE/EE affecting all versions from 17.0 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 authenticated user with Guest access to read confidential epic content meant to be restricted by external authorization, due to incorrect authorization checks. |
|
| CVE-2026-14814 | Oct 13, 2026 |
GitLab CE/EE Cache Poisoning in Raw Repo Files (v<19.2.8,19.3<19.3.5,19.4<19.4.2)GitLab has remediated an issue in GitLab CE/EE affecting all versions before 19.2.8, 19.3 before 19.3.5, and 19.4 before 19.4.2 that, under certain conditions, could have allowed a user to poison cached responses for raw repository files, causing targeted users' CI/CD pipelines to execute specially crafted content and potentially exposing protected environment variables, due to improper validation of repository references. |
|
| CVE-2026-16275 | Oct 13, 2026 |
Unauthenticated Read of Private Notes in GitLab CE/EE (17.4-19.4)GitLab has remediated an issue in GitLab CE/EE affecting all versions from 17.4 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 read confidential notes on public projects due to incorrect authorization checks. |
|
| CVE-2026-16301 | Oct 13, 2026 |
GitLab CE/EE: Auth Bypass in CI/CD Pipeline Creation (18.7-19.4)GitLab has remediated an issue in GitLab CE/EE affecting all versions from 18.7 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 authenticated user with Developer role to execute CI/CD pipelines on protected branches without authorization due to improper authorization checks in the downstream pipeline creation service. |
|
| CVE-2026-78335 | Oct 13, 2026 |
GitLab CE/EE Auth Bypass via Finegranulated PAT (19.2.8, 19.3.5, 19.4.2)GitLab has remediated an issue in GitLab CE/EE affecting all versions from 19.1 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 authenticated user holding a project-scoped fine-grained Personal Access Token to modify integrations belonging to a group outside the token's scope, due to incorrect authorization checks. |
|
| CVE-2026-81839 | Oct 13, 2026 |
GitLab EE Authenticated Pipeline Execution RCE via Policy Records (18.1-19.4.2)GitLab has remediated an issue in GitLab EE affecting all versions from 18.1 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 authenticated user to execute arbitrary CI/CD pipelines in a transferred project with the new group's privileges due to improper cleanup of scheduled pipeline execution policy records. |
|
| CVE-2026-82632 | Oct 13, 2026 |
Unauthorized project import via fine-grained PAT in GitLab 18.919.4GitLab has remediated an issue in GitLab CE/EE affecting all versions from 18.9 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 authenticated user with a fine-grained Personal Access Token scoped only to user-boundary import permissions to import projects into group namespaces beyond the token's intended scope, due to incorrect authorization of the import target namespace. |
|
| CVE-2026-84284 | Oct 13, 2026 |
GitLab CE/EE unauth read of work items (17.1119.4.2)GitLab has remediated an issue in GitLab CE/EE affecting all versions from 17.11 before 19.2.8, 19.3 before 19.3.6, and 19.4 before 19.4.2 that, under certain conditions, could have allowed an unauthenticated user to read work item contents from private groups and projects due to incorrect authorization checks. |
|
| CVE-2026-85529 | Oct 13, 2026 |
GitLab GraphQL API Unauthorized Read of Internal Notes (v19.2-19.4)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 read internal notes and confidential system notes on public projects due to improper authorization in the GraphQL API. |
|
| CVE-2026-92528 | Oct 13, 2026 |
GitLab EE Improper Identity Res. Allows MR Approval (Pre-19.2.8/19.3.5/19.4.2)GitLab has remediated an issue in GitLab EE affecting all versions from 16.11 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 authenticated user to approve a merge request despite having contributed commits to it, due to improper identity resolution. |
|
| CVE-2026-92883 | Oct 13, 2026 |
GitLab CE/EE pre19.2.8/19.3.5/19.4.2 JS exec via repo syntax highlightGitLab has remediated an issue in GitLab CE/EE affecting all versions from 19.1 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 authenticated user to execute arbitrary JavaScript in the context of other users' browser sessions via a specially crafted repository, due to improper sanitization of HTML attributes in syntax-highlighted output. |
|
| CVE-2026-97229 | Oct 13, 2026 |
GitLab CE/EE: Unauth RCE via crafted regex in CI/CD before 19.4.2GitLab 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. |
|
| CVE-2026-96893 | Oct 13, 2026 |
GitLab EE AI Agent Instruction Injection (19.1-19.2.8, 19.3-19.3.5, 19.4-19.4.2)GitLab has remediated an issue in GitLab EE affecting all versions from 19.1 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 authenticated user to inject specially crafted content into AI agent instructions, potentially causing unintended command execution attributed to other users, due to improper neutralization of special elements in AI conversation context construction. |
|
| CVE-2026-100104 | Oct 13, 2026 |
GitLab CE/EE <19.4.2 SSRF via TOCTOU in repo importGitLab has remediated an issue in GitLab CE/EE affecting all versions from 10.3 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 authenticated user to perform server-side request forgery and reach internal network resources due to a time-of-check to time-of-use race condition in URL validation during repository import operations. |
|
| CVE-2026-100755 | Oct 13, 2026 |
GitLab CE/EE <19.2.8 Auth Cache PoisoningGitLab has remediated an issue in GitLab CE/EE affecting all versions from 16.2 before 19.2.8, 19.3 before 19.3.5, and 19.4 before 19.4.2 that, under certain deployment configurations, could have allowed an authenticated user to poison cached page content served to other users due to improper cache key construction. |
|
| CVE-2026-103549 | Oct 13, 2026 |
GitLab <19.4.2 AuthZ Bypass in Package Registry MetadataGitLab has remediated an issue in GitLab CE/EE affecting all versions from 17.6 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 authenticated user with maintainer-role permissions to remove certain package registry metadata that package protection rules restrict to higher roles, due to improper authorization checks. |
|
| CVE-2026-104661 | Oct 13, 2026 |
GitLab EE <19.4.2 Auth Priv Esc via Custom RoleGitLab has remediated an issue in GitLab EE affecting all versions from 17.0 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 authenticated user holding a custom role with compliance framework administration permissions to configure and execute a specially crafted compliance pipeline across group projects due to improper privilege assignment. |
|
| CVE-2026-105458 | Oct 13, 2026 |
GitLab EE <19.2.8, <19.3.5, <19.4.2 Token Bypass in Duo AgentGitLab has remediated an issue in GitLab EE affecting all versions from 19.1 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 authenticated user holding a specific granular permission to obtain a GitLab Duo Agent Platform token that bypasses governance controls, due to reliance on untrusted input in a security decision. |
|
| CVE-2026-1403 | Oct 07, 2026 |
GitLab CE/EE Remote DoS: Sidekiq Crash on CSV Import (v11.7-<18.8.9,18.9-<18.9.5,18.10-<18.10.3)GitLab has remediated an issue in GitLab CE/EE affecting all versions from 11.7 before 18.8.9, 18.9 before 18.9.5, and 18.10 before 18.10.3 that when importing CSV files could have allowed an authenticated user to cause denial of service to Sidekiq workers due to improper validation of CSV file structure. |
|
| CVE-2026-90970 | Oct 02, 2026 |
GitLab AI Gateway Prompt Sandbox Escape CVE-2026-90970 (18.1.6-19.4.1)GitLab 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. |
|
| CVE-2026-4523 | Sep 29, 2026 |
GitLab CE/EE CI/CD Trace Read Auth Flaw 15.11-19.4 via GraphQL APIGitLab has remediated an issue in GitLab CE/EE affecting all versions from 15.11 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 unauthenticated user to read CI/CD job trace contents containing sensitive variable values due to improper authorization enforcement in the GraphQL API. |
|
| CVE-2026-8937 | Sep 29, 2026 |
GitLab CE/EE 19.0-19.4.1 Auth Bypass on Linked Work ItemsGitLab has remediated an issue in GitLab CE/EE affecting all versions from 19.0 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 read private child issue contents, including titles and descriptions, from projects they had no access to, due to missing authorization checks on linked work items within visible epics. |
|
| CVE-2026-10518 | Sep 29, 2026 |
GitLab EE Auth Bypass in EE 17.9-19.4.1: Guest can read private security policyGitLab has remediated an issue in GitLab EE affecting all versions from 17.9 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 with guest-level permissions to read private security policy content they were not authorized to access due to improper authorization enforcement. |
|
| CVE-2026-84739 | Sep 29, 2026 |
GitLab CE/EE XSS in MR Diff Viewer (v19.4.1)GitLab has remediated an issue in GitLab CE/EE affecting all versions from 13.11 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 JavaScript in the context of another user's browser session due to improper sanitization of path components in the merge request diff viewer. |
|
| CVE-2026-89078 | Sep 23, 2026 |
GitLab CE/EE double free in CI/CD regex parsing (19.2-19.4)GitLab 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. |
|
| CVE-2026-92530 | Sep 23, 2026 |
GitLab CE/EE Auth Spoof via Direct Transfer Import (v19.1-19.4)GitLab has remediated an issue in GitLab CE/EE affecting all versions from 19.1 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 spoof merge request authorship and attribute content to arbitrary existing users on the target instance due to improper reliance on ephemeral cache state during Direct Transfer imports. |
|
| CVE-2026-92470 | Sep 23, 2026 |
GitLab EE 18.719.4.1 AuthZ flaw: Auth users read CI/CD vars via Duo AIGitLab has remediated an issue in GitLab EE affecting all versions from 18.7 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 access sensitive CI/CD variable values from debug-mode job traces through the Duo AI troubleshooting feature due to missing authorization checks. |
|
| CVE-2026-92529 | Sep 23, 2026 |
GitLab EE 19.1-19.4 (pre-19.2.7/19.3.3/19.4.1) AI Governance Bypass (Auth)GitLab has remediated an issue in GitLab EE affecting all versions from 19.1 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 with developer-role permissions to bypass admin-configured AI tool governance controls for workflows in namespaces they do not control due to improper authorization checks. |
|
| CVE-2026-92874 | Sep 23, 2026 |
GitLab <19.4 Improper Auth Allows MCP Token Scope EscalationGitLab has remediated an issue in GitLab CE/EE affecting all versions from 18.3 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 with an MCP-scoped token to perform actions beyond the intended scope of that token due to improper authorization checks. |
|
| CVE-2026-92628 | Sep 23, 2026 |
GitLab CE/EE 18.619.4.1 Race Cond in MCP SearchGitLab has remediated an issue in GitLab CE/EE affecting all versions from 18.6 before 19.2.7, 19.3 before 19.3.3, and 19.4 before 19.4.1 that under a race condition, the MCP search tool's shared state handling could have caused search results to be returned under an incorrect user context. |
|
| CVE-2026-93577 | Sep 23, 2026 |
GitLab CE 19.2-19.4 CI/CD Regex Integer Overflow (arbitrary code)GitLab 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. |
|
| CVE-2026-86341 | Sep 16, 2026 |
GitLab EE: Improper Access Control Lets Owner Disable Protected Env ApprovalGitLab has remediated an issue in GitLab EE affecting all versions from 17.1 before 19.1.8, 19.2 before 19.2.6, and 19.3 before 19.3.2 that, under certain conditions, an authenticated user with Owner or Maintainer permissions could have silently disabled protected environment deployment approval requirements, allowing unapproved deployments to reach production, due to improper access control checks performed after the protected resource was modified. |
|
| CVE-2024-11222 | Sep 16, 2026 |
GitLab CE/EE Race Condition in Pipeline Creation (beyond 19.1.8, 19.2.6, 19.3.2)GitLab has remediated an issue in GitLab CE/EE affecting all versions from 13.0 before 19.1.8, 19.2 before 19.2.6, and 19.3 before 19.3.2 that under certain conditions could have allowed a developer user to perform actions in the context of another user's merge request commit due to a race condition issue in pipeline creation. |
|
| CVE-2025-14871 | Sep 16, 2026 |
GitLab GraphQL DoS via Complexity Calculation (v<19.3.2)GitLab has remediated an issue in GitLab CE/EE affecting all versions from 18.4.6 before 19.1.8, 19.2 before 19.2.6, and 19.3 before 19.3.2 that under certain conditions could have allowed an unauthenticated user to cause denial of service due to improper resource allocation limits in the GraphQL complexity calculation logic. |
|