CVE-2026-92530: GitLab Has Remediated an Issue
Affects gitlabSource GCVE Database
Not known to be exploited · CVSS 4.3 Medium · fixed in 19.4.1 : update gitlab when convenient.
Data as of 7 Nov 2026, 23:24 UTC
- EPSS
- 0.1% chance of exploitation in 30 days – higher than 1% 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:N/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 to 19.4.1, 19.3.3 or 19.2.7.
Affected software
| Product | Affected | Fixed in |
|---|---|---|
RubyGemsgitlabpkg:gem/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
GitLab has remediated this issue in versions 19.2.7, 19.3.3, and 19.4.1 and later. Users should upgrade to these fixed versions or later to mitigate this vulnerability. No other mitigation actions are indicated.
Description
A vulnerability in GitLab CE/EE versions from 19.1 before 19.2.7, 19.3 before 19.3.3, and 19.4 before 19.4.1 could allow an authenticated user to spoof merge request authorship and attribute content to arbitrary existing users due to improper reliance on ephemeral cache state during Direct Transfer imports. This issue has been remediated by GitLab.