CVE-2021-22175
KEVGitLab Server-Side Request Forgery (SSRF) Vulnerability
Description
GitLab contains a server-side request forgery (SSRF) vulnerability when requests to the internal network for webhooks are enabled.
When requests to the internal network for webhooks are enabled, a server-side request forgery vulnerability in GitLab affecting all versions starting from 10.5 was possible to exploit for an unauthenticated attacker even on a GitLab instance where registration is disabled
CVSS 3.1 vector
CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:C/C:H/I:N/A:NPublishedJun 11, 2021
Last modifiedOct 1, 2026
Added to KEVFeb 18, 2026
Remediation dueMar 11, 2026
References
- gitlab.com/gitlab-org/cves/-/blob/master/2021/CVE-2021-22175.jsonVendor Advisory
- gitlab.com/gitlab-org/gitlab/-/issues/294178ExploitIssue Tracking
- hackerone.com/reports/1059596Permissions RequiredThird Party Advisory
- cisa.gov/known-exploited-vulnerabilities-catalog?field_cve=CVE-2021-22175US Government Resource
0 recent articles mention this CVE
69
Risk assessment · High
Actively exploited. Patch immediately.
- Exploitation
- Confirmed in the wild (CISA KEV)
- Federal remediation deadline
- Overdue by 229 days
- CVSS
- 6.8 MEDIUM
- EPSS (30-day exploit probability)
- 53.4% · top 1% of all CVEs
- Weakness
- CWE-918
- Attack vector
- Network, remotely reachable
- Preconditions
- No privileges and no user interaction
Recommended actions
- 1.Apply mitigations per vendor instructions, follow applicable BOD 22-01 guidance for cloud services, or discontinue use of the product if mitigations are unavailable.
- 2.Treat as emergency change: patch or isolate internet-facing instances first.
- 3.Review exposure: confirm which instances are reachable from the internet and restrict access until patched.
- 4.Hunt for compromise: review logs for the disclosure window, not just from the patch date.
Assessment is derived automatically from the live signals above; verify against your own asset inventory.