GitLab EE affecting all · GitLab Has Remediated an Issue
Source GCVE Database
Not known to be exploited · CVSS 5.9 Medium · fixed in 19.5.6 : update GitLab when convenient.
Data as of 17 Nov 2026, 07:52 UTC
Thin evidence
One scorer or none| CNA (GitLab) | CVSS 3.1 | 5.9 |
|---|
- Patch
- Available – fixed in 19.5.6, 19.4.8, 19.3.9
CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:H/A:NExploitation evidence
Disclosed: evidence found.
CVE published 17 Nov 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 16 Nov 2026.
What to do
Upgrade GitLab and gitlab-org/gitlab to 19.5.6, 19.4.8 or 19.3.9.
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| GitLabGitLab | Affected
| Fixed in
|
| GitLabGitLab | Affected
| Fixed in
|
| GitLabGitLab | Affected
| Fixed in
|
GitHubgitlab-org/gitlabpkg:github/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 EE to versions 19.3.9, 19.4.8, or 19.5.6 or later where this vulnerability has been remediated. No other mitigation steps are indicated as the issue is fixed in these releases.
Description
A vulnerability in GitLab EE versions from 18.2 before 19.3.9, 19.4 before 19.4.8, and 19.5 before 19.5.6 could allow an attacker controlling an upstream repository to alter cached Maven packages from other repositories within the same virtual registry due to improper response validation. This issue has been remediated in the specified fixed versions.