CVE-2026-92874: GitLab Has Remediated an Issue
Affects gitlabSource GCVE Database
Not known to be exploited · CVSS 5.4 Medium · fixed in 19.4.1 : update gitlab when convenient.
Data as of 6 Nov 2026, 23:24 UTC
- EPSS
- 0.1% chance of exploitation in 30 days – higher than 3% 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:U/C:L/I:L/A:NExploitation evidence
Disclosed: evidence found.
CVE published 24 Sep 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by 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
| Product | Affected | Fixed in |
|---|---|---|
RubyGemsgitlab-org/gitlabpkg:gem/gitlab-org/gitlabOther threats | Affected
| Fixed in
|
Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.
AI-suggested
Upgrade GitLab CE/EE to versions 19.2.7, 19.3.3, or 19.4.1 or later to apply the official fix. Since the vendor has remediated the issue in these versions, applying these updates will mitigate the vulnerability.
Description
A vulnerability in GitLab CE/EE versions from 18.3 before 19.2.7, 19.3 before 19.3.3, and 19.4 before 19.4.1 allows an authenticated user with an MCP-scoped token to perform actions beyond the intended scope due to improper authorization checks. This issue has been remediated in versions 19.2.7, 19.3.3, and 19.4.1. The vulnerability has a medium severity rating with a CVSS score of 5.4.