CVE-2026-92529: 
GitLab vulnerability analysis and mitigation

CVE-2026-92529 is an improper authorization vulnerability in GitLab Enterprise Edition (EE) that allows authenticated users with developer-role permissions to bypass admin-configured AI tool governance controls for workflows in namespaces they do not control. It affects GitLab EE versions 19.1 through 19.2.6, 19.3 through 19.3.2, and 19.4 through 19.4.0. The vulnerability was published on September 24, 2026, and has a CVSS v3.1 base score of 4.3 (Medium) (GitHub Advisory, GitLab Patch Release).

The root cause is classified as CWE-863 (Incorrect Authorization): the product performs an authorization check when an actor attempts to access a resource or perform an action, but does not correctly perform the check. Specifically, under certain conditions, the authorization logic governing AI tool workflow configurations fails to properly validate whether the requesting user has rights over the target namespace, allowing a developer-role user to interact with governance controls in namespaces outside their authority. The attack is network-based, requires low privileges (a valid developer account), no user interaction, and low attack complexity (GitHub Advisory).

Successful exploitation allows an authenticated developer-role user to bypass admin-configured AI tool governance controls and modify workflow configurations in namespaces they are not authorized to control. The integrity impact is limited (low), with no confidentiality or availability impact assessed. While the scope is unchanged and lateral movement potential is limited, the bypass undermines organizational controls over AI tool usage policies, potentially allowing unauthorized AI workflow modifications across multiple namespaces (GitHub Advisory, GitLab Patch Release).

There is no public proof-of-concept exploit available, and no evidence of in-the-wild exploitation has been observed as of the disclosure date. The EPSS score is 0.0, reflecting a very low probability of exploitation in the near term. The vulnerability is not listed in the CISA Known Exploited Vulnerabilities (KEV) catalog. Exploitation requires an authenticated session with at least developer-role permissions, limiting the attack surface to internal or trusted users (GitHub Advisory).

GitLab has released patched versions addressing this vulnerability: upgrade GitLab EE to 19.2.7, 19.3.3, or 19.4.1 (or later) depending on the currently deployed version. After upgrading, administrators should review AI tool governance configurations and audit any workflow changes made by developer-role users in namespaces they do not own. No configuration-based workaround has been published; upgrading is the recommended remediation (GitLab Patch Release, GitHub Advisory).