Skip to content
Cyber Threat
CTI Academy Sponsor CTI Academy
MEDIUM · CVSS 6.8 CISA Known Exploited Vulnerability

CVE-2021-22175

GitLab Server-Side Request Forgery (SSRF) Vulnerability

GitLab GitLab

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
6.8
MEDIUM
EPSS
53.4%
30-day exploitation
Ransomware groups
0
recorded exploiting
Published
11 Jun 2021
CWE-918

Exploitation status

CISA Known Exploited Vulnerabilities

Listed by CISA on 18 February 2026. US federal agencies were required to remediate it by 11 March 2026.

EPSS — exploitation probability

FIRST puts the probability of exploitation activity in the next 30 days at 53.4%, which is higher than 99% of all scored vulnerabilities. EPSS is a forecast of activity, not a measure of severity, and it is rescored daily.

CVSS vector

CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:C/C:H/I:N/A:N

Frequently asked questions

Is CVE-2021-22175 being exploited by ransomware groups?

No ransomware group in this database is currently recorded as exploiting CVE-2021-22175.

What does CVE-2021-22175 affect?

CVE-2021-22175 affects GitLab GitLab. 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

How severe is CVE-2021-22175?

CVE-2021-22175 is rated MEDIUM with a CVSS base score of 6.8. EPSS puts the probability of exploitation in the next 30 days at 53.4%, higher than 99% of all scored vulnerabilities. It is listed in the CISA Known Exploited Vulnerabilities catalog, with a federal remediation deadline of 11 March 2026.

How should organisations respond to CVE-2021-22175?

Apply the vendor patch for GitLab GitLab as the first priority, and treat any internet-facing instance as the most urgent. Because this vulnerability is associated with ransomware activity, also review whether the affected systems were reachable before patching, rather than assuming that patching alone closes the incident.