CVE-2026-7471 json
Server-Side Request Forgery (SSRF) in GitLab
published 5mo ago modified 8h ago also BIT-gitlab-2026-7471 , EUVD-2026-30239
- cvss
- 3.5
- version 3.1, CNA
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 0.2%
- EPSS 0.2% chance of exploitation in 30 days, percentile 6%
- public exploits
- 0
- none known
Summary
GitLab has remediated an issue in GitLab EE affecting all versions from 18.8 before 18.9.7, 18.10 before 18.10.6, and 18.11 before 18.11.3 that could have allowed an authenticated user with control of a virtual registry upstream to make requests to internal hosts due to improper validation.
Patch / fix
- bitnami gitlab 18.9.7, 18.10.6, 18.11.3
- GitLab GitLab 18.9.7, 18.10.6, 18.11.3
Is CVE-2026-7471 in your dependencies? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.
Check with FencerCISA SSVC
- Exploitation
- none
- Automatable
- no
- Technical impact
- partial
- Assessed
- 5mo ago
Exploit prediction
0.17% chance of exploitation in the next 30 days, higher than 6% of all scored CVEs (FIRST EPSS, 2026-11-11).
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| CNA | 3.1 | 3.5 | CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:C/C:L/I:N/A:N |
| OSV | 3.1 | 3.5 | CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:C/C:L/I:N/A:N |
Affected packages
| ecosystem | package | affected | fixed in |
|---|---|---|---|
| bitnami | gitlab | >=18.8.0, <18.9.7 >=18.10.0, <18.10.6 >=18.11.0, <18.11.3 |
18.9.7 18.10.6 18.11.3 |
Affected products
- GitLab GitLab
Classification
- Weakness
-
- CWE-918 Server-Side Request Forgery
- Technology feeds
References
-
gitlab.com
/gitlab-org/gitlab/-/work_items/594196
broken-link, web
-
about.gitlab.com
/releases/2026/05/13/patch-release-gitlab-18-11-3-released/
release-notes, article
-
nvd.nist.gov
/vuln/detail/CVE-2026-7471
web
Sources
- CVE List CVE-2026-7471
- NVD CVE-2026-7471
- OSV BIT-gitlab-2026-7471
Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.