CVE-2021-22175
CriticalExploitedPublic exploitWhen 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
Published Jun 11, 2021 · Updated Oct 3, 2026 · Also known as BIT-gitlab-2021-22175, UBUNTU-CVE-2021-22175
Key Facts
Patch immediately- CVE-2021-22175 is a critical-severity vulnerability (CVSS 9.8 v3.1) affecting GitLab.
- It is exploited in the wild, listed in CISA KEV, Industry KEV feed, CIRCL KEV, ENISA EUVD since Mar 11, 2025. Public exploit code is available.
- EPSS estimates a 53% probability of exploitation in the next 30 days.
- Fixed versions are available, including GitLab 13.6.7, GitLab 13.7.7, GitLab 13.8.4.
- Brandefense priority: patch immediately, because it is listed as exploited in the wild.
CVSS v3.1
9.8
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
EPSS (30-day exploit likelihood)
53%
Higher than 98.9% of all scored CVEs
Exploited in the wild
Yes
4 catalog listings
Public exploit code
Available
Proof-of-concept or weaponized module
Get the full CVE-2021-22175 brief as a PDF
Every affected product and fixed release, exploitation status and a first 24 hours response checklist, emailed within minutes.
Description
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
Known-Exploited Catalog Listings
| Catalog | Added | Remediation due | Ransomware use |
|---|---|---|---|
| CISA KEV | Feb 18, 2026 | Mar 11, 2026 | Not reported |
| Industry KEV feed | Mar 11, 2025 | Mar 11, 2026 | Not reported |
| CIRCL KEV | Feb 18, 2026 | Mar 11, 2026 | Not reported |
| ENISA EUVD | Feb 18, 2026 | n/a | Not reported |
Required action: Apply mitigations per vendor instructions, follow applicable BOD 22-01 guidance for cloud services, or discontinue use of the product if mitigations are unavailable.
Affected Products
6 affected entries in total| Product | Affected versions | Fixed in |
|---|---|---|
| GitLabGitlab | >= 10.5.0, >= >=10.5, <13.6.7 | 13.6.7 |
Patched Releases
GitLab
13.6.7, 13.7.7, 13.8.4, 15.10.8+ds1-2
Timeline
Publicly disclosed
Jun 11, 2021
Added to Industry KEV feed
Mar 11, 2025
Added to CISA KEV
Feb 18, 2026
Added to CIRCL KEV
Feb 18, 2026
Added to ENISA EUVD
Feb 18, 2026
Last updated
Oct 3, 2026
Weakness Type
- CWE-918 Server-Side Request Forgery (SSRF)
References
- advisoryhttps://gitlab.com/gitlab-org/cves/-/blob/master/2021/CVE-2021-22175.json
- advisoryhttps://hackerone.com/reports/1059596
- advisoryhttps://ubuntu.com/security/CVE-2021-22175
- advisoryhttps://www.cisa.gov/known-exploited-vulnerabilities-catalog
- advisoryhttps://www.cve.org/CVERecord?id=CVE-2021-22175
FAQ
Common Questions.
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
Affected: GitLab versions >= 10.5.0, >= >=10.5, <13.6.7. The full list is in the CVE brief.
It is exploited in the wild, listed in CISA KEV, Industry KEV feed, CIRCL KEV, ENISA EUVD since Mar 11, 2025.
Yes. It was added on Feb 18, 2026 with a federal remediation due date of Mar 11, 2026.
Public exploit code is available.
Fixed versions are available, including GitLab 13.6.7, GitLab 13.7.7, GitLab 13.8.4.
Brandefense priority: patch immediately, because it is listed as exploited in the wild.
Is CVE-2021-22175 Running On Your Attack Surface?
Brandefense maps vulnerabilities like this one to your internet-facing assets and tells you exactly where to patch.
Request A Demo