CVE-2026-7471: GitLab · Server-Side Request Forgery
Affects GitLabSource GCVE Database
Not known to be exploited · CVSS 3.5 Low · fixed in 18.11.3 : update GitLab when convenient.
Data as of 11 Nov 2026, 23:08 UTC
Thin evidence
One scorer or none| CNA (GitLab) | CVSS 3.1 | 3.5 |
|---|
- Patch
- Available – fixed in 18.11.3, 18.10.6, 18.9.7
CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:C/C:L/I:N/A:NExploitation evidence
Disclosed: evidence found.
CVE published 14 May 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 11 Nov 2026.
What to do
Upgrade GitLab to 18.11.3, 18.10.6 or 18.9.7.
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| GitLab GitLab | Affected
| Fixed in
|
AI-suggested
GitLab has remediated this vulnerability in versions 18.9.7, 18.10.6, and 18.11.3. Users should upgrade affected GitLab EE instances to these or later versions to mitigate the issue. No additional mitigation steps are indicated by the vendor advisory.
Description
CVE-2026-7471 is a server-side request forgery (SSRF) vulnerability in GitLab Enterprise Edition affecting versions 18.8 before 18.9.7, 18.10 before 18.10.6, and 18.11 before 18.11.3. It allows an authenticated user with control over a virtual registry upstream to send requests to internal hosts due to improper validation. The vulnerability has a low severity score and no known exploitation in the wild.