Skip to main content
VulnerabilityPublished

CVE-2026-92470: GitLab Has Remediated an Issue

Affects gitlabSource GCVE Database

0
Compare

Not known to be exploited · CVSS 7.7 High · fixed in 19.4.1 : patch gitlab soon.

Data as of 7 Nov 2026, 23:24 UTC

CVSS 3.1 base score
7.7High
How severe the flaw is on the 0–10 CVSS scale.
EPSS
0.2% chance of exploitation in 30 days – higher than 11% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
Patch
Available – fixed in 19.4.1, 19.3.3, 19.2.7
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:N/A:N

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 24 Sep 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponized: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 7 Nov 2026.

What to do

Upgrade gitlab-org/gitlab to 19.4.1, 19.3.3 or 19.2.7.

Affected software

ProductAffectedFixed in
GitHubgitlab-org/gitlabpkg:github/gitlab-org/gitlabOther threatsAffected
  • >=18.7 <19.2.7
  • >=19.3 <19.3.3
  • >=19.4 <19.4.1
Fixed in
  • 19.2.7
  • 19.3.3
  • 19.4.1

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

AI-suggested

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.

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.

References

Community reviews

Loading reviews…