CVE-2021-22175
GitLab Server-Side Request Forgery (SSRF)
- Published11 Jun 2021
- Added to CISA KEV18 Feb 2026
- Remediation due11 Mar 2026
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
CVSS 3.1 breakdown
CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:C/C:H/I:N/A:NAffected products
Remediation
References
Related CVEs
Recent high-severity vulnerabilities sharing a weakness type.
Frequently asked
Is CVE-2021-22175 being actively exploited?
Yes. CVE-2021-22175 is listed in the CISA Known Exploited Vulnerabilities (KEV) catalog, added 18 Feb 2026.
How severe is CVE-2021-22175?
CVE-2021-22175 has a CVSS 3.1 base score of 6.8, rated medium. EPSS estimates a 53.4% probability of exploitation.
Which products are affected by CVE-2021-22175?
Affected products include GitLab.
How do I fix CVE-2021-22175?
Upgrade affected software to a fixed version, for example GitLab 13.6.7 or later, then confirm no affected versions remain in your inventory.
How Secuno handles this
Secuno correlates vulnerabilities like CVE-2021-22175 against the real software inventory on every managed device, as each hourly inventory arrives. Rather than a static severity, each match is scored in context: exploit availability, EPSS, the asset's exposure, and business criticality decide where it lands in the queue. Because it is on the CISA KEV list, a risk for it never ranks below high, and the update that fixes it moves to the Emergency patch lane. If an affected version is present anywhere across your portfolio, it surfaces automatically with a prioritised remediation path.
Data from the NVD, CISA KEV catalog and FIRST EPSS. CVSS 3.1 base score shown where available.