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… (CVE-2026-92470)
A vulnerability in GitLab EE versions from 18.7 up to but not including 19.2.7, 19.3 up to but not including 19.3.3, and 19.4 up to but not including 19.4.1 could allow an authenticated user to access sensitive CI/CD variable values via debug-mode job traces through the Duo AI troubleshooting feature due to missing authorization checks. This issue has been remediated in versions 19.2.7, 19.3.3, and 19.4.1.
AI Analysis
Technical Summary
CVE-2026-92470 describes an authorization bypass vulnerability in GitLab EE affecting versions from 18.7 before 19.2.7, 19.3 before 19.3.3, and 19.4 before 19.4.1. Under certain conditions, an authenticated user could exploit missing authorization checks in the Duo AI troubleshooting feature to access sensitive CI/CD variable values exposed in debug-mode job traces. This could lead to disclosure of sensitive information. The vulnerability has been fixed in GitLab EE versions 19.2.7, 19.3.3, and 19.4.1.
Potential Impact
The vulnerability allows an authenticated user with limited privileges to access sensitive CI/CD variables, which could lead to exposure of secrets or credentials used in CI/CD pipelines. The CVSS score of 7.7 (high) reflects the network attack vector, low attack complexity, and high confidentiality impact without integrity or availability impact.
Mitigation Recommendations
A fix is available and has been released in GitLab EE versions 19.2.7, 19.3.3, and 19.4.1. Users should upgrade affected GitLab EE instances to these versions or later to remediate the vulnerability. No additional mitigation steps are indicated by the vendor advisory.
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… (CVE-2026-92470)
Description
A vulnerability in GitLab EE versions from 18.7 up to but not including 19.2.7, 19.3 up to but not including 19.3.3, and 19.4 up to but not including 19.4.1 could allow an authenticated user to access sensitive CI/CD variable values via debug-mode job traces through the Duo AI troubleshooting feature due to missing authorization checks. This issue has been remediated in versions 19.2.7, 19.3.3, and 19.4.1.
CVSS v3.1
Score 7.7high
Affected software
pkg:github/gitlab-org/gitlabRun on your own infrastructure? Check whether these packages are installed with threat-finder — our free open-source scanner.
Weaknesses
AI-Powered Analysis
Machine-generated threat intelligence
Technical Analysis
CVE-2026-92470 describes an authorization bypass vulnerability in GitLab EE affecting versions from 18.7 before 19.2.7, 19.3 before 19.3.3, and 19.4 before 19.4.1. Under certain conditions, an authenticated user could exploit missing authorization checks in the Duo AI troubleshooting feature to access sensitive CI/CD variable values exposed in debug-mode job traces. This could lead to disclosure of sensitive information. The vulnerability has been fixed in GitLab EE versions 19.2.7, 19.3.3, and 19.4.1.
Potential Impact
The vulnerability allows an authenticated user with limited privileges to access sensitive CI/CD variables, which could lead to exposure of secrets or credentials used in CI/CD pipelines. The CVSS score of 7.7 (high) reflects the network attack vector, low attack complexity, and high confidentiality impact without integrity or availability impact.
Mitigation Recommendations
A fix is available and has been released in GitLab EE versions 19.2.7, 19.3.3, and 19.4.1. Users should upgrade affected GitLab EE instances to these versions or later to remediate the vulnerability. No additional mitigation steps are indicated by the vendor advisory.
Technical Details
- Gcve Source
- db.gcve.eu
- Osv Id
- GHSA-f2v3-pf6x-rw2j
- Osv Schema Version
- 1.4.0
- Aliases
- ["CVE-2026-92470"]
- Database Specific Severity
- HIGH
- Cvss Version
- 3.1
Threat ID: 6ab4be1df7a7c54106eee6bd
Added to database: 09/24/2026, 06:07:25 UTC
Last enriched: 09/24/2026, 06:16:39 UTC
Last updated: 09/25/2026, 04:17:39 UTC
Views: 94
Community Reviews
0 reviewsCrowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.
Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.
Actions
Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.
Need more coverage?
Upgrade to Pro Console for AI refresh and higher limits.
For incident response and remediation, OffSeq services can help resolve threats faster.
Latest Threats
Check if your credentials are on the dark web
Instant breach scanning across billions of leaked records. Free tier available.