CVE-2026-92470
Received Received - Intake

Authentication Bypass in GitLab EE via Duo AI

Publication date: 2026-09-24

Last updated on: 2026-09-24

Assigner: GitLab Inc.

Description
GitLab 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.

CVSS Scores

EPSS Scores

Probability:
Percentile:

Meta Information

Published
2026-09-24
Last Modified
2026-09-24
Generated
2026-09-24
AI Q&A
2026-09-24
EPSS Evaluated
N/A
NVD
CVE-2026-92470
EUVD
EUVD-2026-85734

Affected Vendors & Products

Showing 3 associated CPEs
Vendor Product Version / Range
gitlab gitlab_ee From 18.7 (inc) to 19.2.7 (exc)
gitlab gitlab_ee From 19.3 (inc) to 19.3.3 (exc)
gitlab gitlab_ee From 19.4 (inc) to 19.4.1 (exc)

Helpful Resources

Exploitability

CWE
CWE Icon
KEV
KEV Icon
CWE ID Description
CWE-862 The product does not perform an authorization check when an actor attempts to access a resource or perform an action.

Attack-Flow Graph

AI Quick Actions

Instant insights powered by AI
Executive Summary

This vulnerability in GitLab EE allows an authenticated user to access sensitive CI/CD variable values from debug-mode job traces through the Duo AI troubleshooting feature. The issue occurs due to missing authorization checks in versions before 19.2.7, 19.3.3, and 19.4.1.

Detection Guidance

This vulnerability involves missing authorization checks in GitLab EE's Duo AI troubleshooting feature. To detect it, check GitLab server logs for unauthorized access to CI/CD variable values in debug-mode job traces. Look for logs indicating access to sensitive variables through Duo AI features in versions 18.7 to 19.4 before patched versions.

Impact Analysis

An attacker with access could steal sensitive CI/CD variables, potentially exposing secrets like API keys or passwords. This could lead to unauthorized access to systems, data breaches, or further attacks on your infrastructure.

Compliance Impact

This vulnerability could lead to unauthorized access to sensitive CI/CD variable values, which may include personal data or protected health information. Such exposure risks violating GDPR's data protection principles and HIPAA's confidentiality requirements, depending on the data processed in the affected GitLab instances.

Mitigation Strategies

Upgrade GitLab EE to a patched version: 19.2.7, 19.3.3, or 19.4.1 or later to address the missing authorization checks in the Duo AI troubleshooting feature.

Chat Assistant

Ask questions about this CVE
Hi! I’m here to help you understand CVE-2026-92470. Ask me anything about the vulnerability, its impact, or mitigation strategies.
0/70

EPSS Chart