CVE-2026-92529

Analyzed Analyzed - Analysis Complete

Authenticated Developer Bypass of AI Tool Governance in GitLab EE

Publication date: 2026-09-24

Last updated on: 2026-09-28

Assigner: GitLab Inc.

Description

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.

CVSS Scores

EPSS Scores

Probability:
Percentile:

Meta Information

Published

2026-09-24

Last Modified

2026-09-28

Generated

2026-10-14

AI Q&A

2026-09-24

EPSS Evaluated

2026-10-13

NVD

CVE-2026-92529

EUVD

EUVD-2026-85733

Affected Vendors & Products

Vendor	Product	Version / Range
gitlab	gitlab	From 19.3.0 (inc) to 19.3.3 (exc)
gitlab	gitlab	19.4.0
gitlab	gitlab	From 19.1.0 (inc) to 19.2.7 (exc)

Helpful Resources

Exploitability

CWE

KEV

CWE ID	Description
CWE-863	The product performs an authorization check when an actor attempts to access a resource or perform an action, but it does not correctly perform the check.

Attack-Flow Graph

Executive Summary

This vulnerability in GitLab EE allows an authenticated user with developer-role permissions to bypass admin-configured AI tool governance controls for workflows in namespaces they do not control. This happens due to improper authorization checks in versions 19.1 before 19.2.7, 19.3 before 19.3.3, and 19.4 before 19.4.1.

Detection Guidance

This vulnerability involves improper authorization checks in GitLab EE. To detect it, check your GitLab version against the affected ranges (19.1 before 19.2.7, 19.3 before 19.3.3, 19.4 before 19.4.1). Run 'sudo gitlab-rake gitlab:env:info' to check the version. If you are running an affected version, update to 19.2.7, 19.3.3, or 19.4.1 or later.

Impact Analysis

An attacker with developer permissions could bypass AI tool restrictions, potentially leading to unauthorized access or misuse of AI features in workflows outside their control. This may result in data leaks, policy violations, or unintended AI tool usage.

Compliance Impact

This vulnerability could lead to non-compliance with GDPR or HIPAA by allowing unauthorized access to sensitive data through bypassed AI tool controls. Organizations using affected GitLab versions may face regulatory penalties or data protection violations.

Mitigation Strategies

Upgrade GitLab EE to version 19.2.7, 19.3.3, or 19.4.1 or later to address the authorization bypass issue.

Hi! I’m here to help you understand CVE-2026-92529. Ask me anything about the vulnerability, its impact, or mitigation strategies.

0/70