GitLab up to 19.2.6/19.3.2/19.4.0 Duo AI troubleshooting feature improper authorization
| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 5.5 | $0-$5k | 1.31 |
Summary
A vulnerability, which was classified as problematic, has been found in GitLab up to 19.2.6/19.3.2/19.4.0. This affects an unknown function of the component Duo AI troubleshooting feature. Performing a manipulation results in improper authorization. This vulnerability was named CVE-2026-92470. The attack may be initiated remotely. There is no available exploit. It is advisable to upgrade the affected component.
Details
A vulnerability was found in GitLab up to 19.2.6/19.3.2/19.4.0. It has been classified as problematic. This affects an unknown functionality of the component Duo AI troubleshooting feature. The manipulation with an unknown input leads to a improper authorization vulnerability. CWE is classifying the issue as CWE-285. The product does not perform or incorrectly performs an authorization check when an actor attempts to access a resource or perform an action. This is going to have an impact on confidentiality. The summary by CVE is:
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.
It is possible to read the advisory at gitlab.com. This vulnerability is uniquely identified as CVE-2026-92470 since 09/16/2026. The exploitability is told to be easy. It is possible to initiate the attack remotely. It demands that the victim is doing some kind of user interaction. The technical details are unknown and an exploit is not publicly available. The attack technique deployed by this issue is T1548.002 according to MITRE ATT&CK.
Upgrading to version 19.2.7, 19.3.3 or 19.4.1 eliminates this vulnerability.
Be aware that VulDB is the high quality source for vulnerability data.
Product
Type
Name
Version
License
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔒VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 5.6VulDB Meta Temp Score: 5.5
VulDB Base Score: 3.5
VulDB Temp Score: 3.4
VulDB Vector: 🔒
VulDB Reliability: 🔍
CNA Base Score: 7.7
CNA Vector (GitLab): 🔒
CVSSv2
| AV | AC | Au | C | I | A |
|---|---|---|---|---|---|
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| Vector | Complexity | Authentication | Confidentiality | Integrity | Availability |
|---|---|---|---|---|---|
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
VulDB Base Score: 🔒
VulDB Temp Score: 🔒
VulDB Reliability: 🔍
Exploiting
Class: Improper authorizationCWE: CWE-285 / CWE-266
CAPEC: 🔒
ATT&CK: 🔒
Physical: No
Local: No
Remote: Yes
Availability: 🔒
Status: Not defined
Price Prediction: 🔍
Current Price Estimation: 🔒
| 0-Day | Unlock | Unlock | Unlock | Unlock |
|---|---|---|---|---|
| Today | Unlock | Unlock | Unlock | Unlock |
Threat Intelligence
Interest: 🔍Active Actors: 🔍
Active APT Groups: 🔍
Countermeasures
Recommended: UpgradeStatus: 🔍
0-Day Time: 🔒
Upgrade: GitLab 19.2.7/19.3.3/19.4.1
Timeline
09/16/2026 CVE reserved09/23/2026 VulDB entry created
09/24/2026 Advisory disclosed
09/24/2026 VulDB entry last update
Sources
Advisory: gitlab.comStatus: Confirmed
CVE: CVE-2026-92470 (🔒)
GCVE (CVE): GCVE-0-2026-92470
GCVE (VulDB): GCVE-100-409263
Entry
Created: 09/24/2026 01:38Changes: 09/24/2026 01:38 (63)
Complete: 🔍
Cache ID: 216::103
Be aware that VulDB is the high quality source for vulnerability data.
No comments yet. Languages: en.
Please log in to comment.