CVE-2026-92470Network attack vectorHinoki check available

Authenticated CI/CD variable disclosure via Duo troubleshooting

Published Sep 23, 2026 · Updated Sep 23, 2026

Missing authorization in affected GitLab EE releases before 19.2.7, 19.3.3, or 19.4.1 allows remote authenticated users to read sensitive CI/CD variable values. The Duo AI troubleshooting feature can retrieve debug-mode job traces without checking whether the requesting user is authorized to view variable values embedded in those traces. Exploitation requires an authenticated account, Duo AI troubleshooting, and a debug-mode trace containing sensitive output; the documented consequence is disclosure only.

CVSS severity7.7
High
EPSS probability0.21%
Next 30 days · Oct 19, 2026
Known exploitationUnconfirmed
Based on sourced intelligence
Hinoki checkAvailable
Coverage for this vulnerability

See if you're affected

Explore vulnerability checks for your environment with Hinoki.

Get started

Summary

What happened

Missing authorization in affected GitLab EE releases before 19.2.7, 19.3.3, or 19.4.1 allows remote authenticated users to read sensitive CI/CD variable values. The Duo AI troubleshooting feature can retrieve debug-mode job traces without checking whether the requesting user is authorized to view variable values embedded in those traces. Exploitation requires an authenticated account, Duo AI troubleshooting, and a debug-mode trace containing sensitive output; the documented consequence is disclosure only.

The record

CVE
CVE-2026-92470
Published
Sep 23, 2026
Updated
Sep 23, 2026
Vendor
GitLab
Product
GitLab
Classifications
CWE-862, T1552.001
Attack vector
network
Privileges
authenticated

Timeline

How it unfolded

  1. Sep 23, 2026CVE publishedPublication date reported by the CVE source.
  2. Sep 23, 2026Record updatedLatest update available in the CVE record.

Exploitability

Present is not the same as exploitable

Compare your product and version with the public record. A matching version still requires validation against your environment.

Is a vulnerable build present?

Compare these published version ranges with your installed build and any vendor patches.

  1. Affected versionversion=18.7 <19.2.7
  2. Affected versionversion=19.3 <19.3.3
  3. Affected versionversion=19.4 <19.4.1

What conditions does exploitation require?

Attack vectornetwork
Required privilegesauthenticated

What is affected?

GitLab · GitLabversion=18.7 <19.2.7; version=19.3 <19.3.3; version=19.4 <19.4.1

Published CVSS scores

7.7GitLabCVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:N/A:N

CVSS describes severity. EPSS estimates exploitation probability.

Attacks

What attackers are doing with it

Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.

Activity data is delayed. The latest report is Sep 28, 2026.

Daily unique IPsNo honeypot observations are available for this CVE in the selected window.

No observations available

Sep 22, 2026Sep 28, 2026
Latest reporting daySep 28, 2026
Latest daily unique IPsUnavailable
Prior 30-day averageUnavailable
SourceShadowserver honeypots (KEV)
Vectornetwork
Privilegesauthenticated
Known exploitationUnconfirmed
Public exploitUnconfirmed

Weakness, pattern, technique

CWE-862Missing Authorization
T1552.001Credentials from Files

Public exploit references

No public exploit references are available in this record.

Labels summarize the accepted research assessment. They do not indicate a test against your environment.

Technologies

Your stack

See the directory against your own environment.

Your stack

Check the software in your environment

Get started to see how Hinoki identifies affected software and validates exploitability in your environment.

Get started