CVE-2026-92529: GitLab AI Governance Auth Bypass Vulnerability

CVE-2026-92529 Overview

CVE-2026-92529 is an improper authorization vulnerability [CWE-863] in GitLab Enterprise Edition (EE). The flaw allows an authenticated user with developer-role permissions to bypass admin-configured AI tool governance controls for workflows in namespaces they do not control. The vulnerability affects GitLab EE versions 19.1 before 19.2.7, 19.3 before 19.3.3, and 19.4 before 19.4.1. GitLab remediated the issue in the 19.4.1 patch release.

Critical Impact
Authenticated developers can bypass AI tool governance policies set by administrators, undermining namespace-level controls on how AI workflows execute within GitLab EE environments.

Affected Products

GitLab EE versions 19.1 through 19.2.6
GitLab EE versions 19.3 through 19.3.2
GitLab EE version 19.4.0

Discovery Timeline

2026-09-24 - CVE-2026-92529 published to NVD
2026-09-28 - Last updated in NVD database

Technical Details for CVE-2026-92529

Vulnerability Analysis

The vulnerability resides in the authorization layer that governs AI tool usage within GitLab EE workflows. GitLab administrators can configure governance controls that restrict which AI tools may run within specific namespaces. Under certain conditions, these controls fail to enforce the namespace boundary.

An authenticated user holding developer-role permissions can trigger AI tool workflows targeting namespaces they do not own or administer. The authorization check does not correctly validate the relationship between the acting user, the target namespace, and the admin-defined governance policy. As a result, policy enforcement is skipped for the affected code path.

The impact is limited to integrity of governance controls. The vulnerability does not expose confidential data directly, nor does it disrupt service availability. However, it undermines the trust model for AI usage policies in multi-tenant GitLab EE deployments.

Root Cause

The root cause is an improper authorization check [CWE-863] in the AI workflow dispatch logic. The code evaluates whether the user can execute an AI workflow but does not re-check whether the admin-configured governance policy applies to the target namespace. This permits a cross-namespace policy bypass by a user who already holds developer access to some namespace in the instance.

Attack Vector

The attack requires network access to the GitLab EE instance and authenticated developer-level credentials. No user interaction is required. The attacker invokes AI tool workflows through standard GitLab API or UI paths while targeting a namespace governed by stricter AI tool policies than those the attacker should be subject to. The vulnerability manifests at the authorization boundary; see GitLab Work Item #605431 for technical details.

Detection Methods for CVE-2026-92529

Indicators of Compromise

AI workflow executions initiated by developer-role users in namespaces where they lack owner or maintainer permissions.
Audit log entries showing AI tool invocations that contradict the governance policy configured for the target namespace.
Unexpected AI tool activity against protected or restricted projects immediately preceding patch deployment.

Detection Strategies

Review GitLab audit events for AI workflow dispatch actions correlated with user role and target namespace.
Compare observed AI tool usage against the admin-configured governance matrix to identify policy violations.
Query GitLab API endpoints exposing workflow run history and filter by actor role versus namespace membership.

Monitoring Recommendations

Enable and centralize GitLab audit logs for all AI tool and workflow operations.
Alert on AI workflow executions where the acting user's role does not match the expected policy scope for the namespace.
Baseline normal AI tool usage per namespace and flag deviations after upgrading to a patched version.

How to Mitigate CVE-2026-92529

Immediate Actions Required

Upgrade GitLab EE to version 19.2.7, 19.3.3, or 19.4.1 or later as applicable to your deployment branch.
Audit AI tool governance policies and verify configuration remains intact after upgrade.
Review recent AI workflow activity by developer-role users for policy violations prior to patching.

Patch Information

GitLab released fixed versions 19.2.7, 19.3.3, and 19.4.1. Full details are available in the GitLab Patch Release 19.4.1 advisory. Self-managed GitLab EE operators should prioritize upgrading instances where developer-role users have access across namespaces governed by distinct AI tool policies.

Workarounds

Temporarily restrict developer-role permissions in affected namespaces until the patch is applied.
Disable or restrict AI tool workflows at the instance level if upgrading is delayed.
Tighten namespace membership and role assignments to minimize cross-namespace policy exposure.

bash

# Verify installed GitLab EE version
gitlab-rake gitlab:env:info | grep -i version

# Upgrade example for Omnibus GitLab EE (Debian/Ubuntu)
sudo apt-get update
sudo apt-get install gitlab-ee=19.4.1-ee.0