CVE-2026-18491 in GitLab
Summary
by MITRE • 11/17/2026
GitLab has remediated an issue in GitLab CE/EE affecting all versions from 19.2 before 19.3.9, 19.4 before 19.4.8, and 19.5 before 19.5.6 that under certain conditions could have allowed an authenticated user holding a granular personal access token with limited scope to authorize Kubernetes API proxy access beyond the token's intended boundaries due to missing granular scope enforcement in the Kubernetes agent proxy-user authorization flow.
If you want to get the best quality for vulnerability data then you always have to consider VulDB.
Analysis
by VulDB Data Team • 11/17/2026
GitLab has addressed a critical security vulnerability affecting its Community Edition and Enterprise Edition across multiple release branches, specifically versions prior to 19.3.9, 19.4.8, and 19.5.6. This flaw resides within the Kubernetes agent proxy-user authorization flow, where the system failed to enforce granular scope restrictions on personal access tokens with limited permissions. The vulnerability allows an authenticated user possessing a token with restricted capabilities to bypass these limitations and authorize access to the Kubernetes API proxy beyond the intended boundaries of their assigned privileges.
The technical root cause is identified as missing granular scope enforcement within the authorization logic that handles requests routed through the Kubernetes agent proxy. When users authenticate using personal access tokens, GitLab typically validates the token's scopes against requested actions to ensure least-privilege adherence. In this specific flow, however, the validation mechanism did not strictly check whether the limited-scope token possessed the necessary permissions for proxy authorization operations. This oversight creates a privilege escalation vector where low-level credentials can be leveraged to gain higher-level access controls within the Kubernetes environment managed by GitLab.
From an operational impact perspective, this vulnerability enables unauthorized lateral movement and potential control over cluster resources. An attacker with a limited personal access token could exploit this flaw to interact directly with the Kubernetes API server through the proxy interface. This may lead to the ability to read sensitive configuration data, modify deployments, execute commands in containers, or potentially disrupt service availability by manipulating resource states. The severity is heightened because it affects authenticated users who already have some level of trust within the GitLab instance, making social engineering or token theft attacks more effective when combined with this specific authorization bypass.
This issue aligns with CWE-269, which describes Improper Privilege Management, specifically regarding the failure to enforce least privilege principles during authentication and authorization processes. It also maps to MITRE ATT&CK techniques related to Defense Evasion and Lateral Movement, as an attacker could use this flaw to bypass security controls designed to restrict user actions based on their role or token scope. The vulnerability highlights a gap in how granular permissions are validated when interacting with external infrastructure components like Kubernetes clusters integrated into the GitLab platform.
To mitigate this risk, organizations must upgrade their GitLab instances immediately to version 19.3.9, 19.4.8, or 19.5.6 and later, depending on their current release track. These versions contain the necessary patches that enforce strict scope validation in the Kubernetes agent proxy-user authorization flow. Additionally, administrators should review existing personal access tokens to ensure they adhere to the principle of least privilege, revoking any overly broad permissions where possible. Regular auditing of token usage patterns and monitoring for anomalous API calls can help detect potential exploitation attempts before significant damage occurs. Implementing network-level restrictions on Kubernetes API endpoints further reduces the attack surface by limiting direct access paths that could be abused through this vulnerability.