CVE-2018-19571 in the critical feed json
GitLab CE/EE, versions 8.18 up to 11.x before 11.3.11, 11.4 before 11.4.8, and 11.5 before 11.5.1, are vulnerable to an SSRF vulnerability…
published 7y ago modified 4mo ago also EUVD-2018-11260
- cvss
- 7.7
- version 3.1, NVD
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 31.5%
- EPSS 31.5% chance of exploitation in 30 days, percentile 98%
- public exploits
- 2
- Exploit-DB
Summary
GitLab CE/EE, versions 8.18 up to 11.x before 11.3.11, 11.4 before 11.4.8, and 11.5 before 11.5.1, are vulnerable to an SSRF vulnerability in webhooks.
Patch / fix
- gitlab gitlab 11.3.11, 11.4.8, 11.5.1
Is CVE-2018-19571 in your stack? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.
Check with FencerTimeline
- Published
- First public exploit (EDB-49257)
Exploit prediction
31.55% chance of exploitation in the next 30 days, higher than 98% of all scored CVEs (FIRST EPSS, 2026-11-09).
Exploits and checks
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| NVD | 3.1 | 7.7 | CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:N/A:N |
| NVD | 2.0 | 4.0 | AV:N/AC:L/Au:S/C:P/I:N/A:N |
Classification
- Weakness
-
- CWE-918 Server-Side Request Forgery
- Technology feeds
References
-
about.gitlab.com
/2018/11/28/security-release-gitlab-11-dot-5-dot-1-released/
broken-link, release-notes, vendor-advisory
-
gitlab.com
/gitlab-org/gitlab-ce/issues/53242
issue-tracking, vendor-advisory
-
packetstormsecurity.com
/files/160516/GitLab-11.4.7-Remote-Code-Execution.html
third-party-advisory, vdb-entry
-
packetstormsecurity.com
/files/160699/GitLab-11.4.7-Remote-Code-Execution.html
third-party-advisory, vdb-entry
Sources
- CVE List CVE-2018-19571
- NVD CVE-2018-19571
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.