CVE-2021-22175 GitLab Server-Side Request Forgery (SSRF)

Exploited in the wild Medium 6.8 Published 11 Jun 2021 Updated 1 Oct 2026

Unauthenticated attackers can exploit SSRF in GitLab webhooks when internal network requests are enabled, potentially accessing internal resources.

Exploited in the wild: Since 18 Feb 2026
Login needed: Not needed
Attackable: Over the internet
Victim action needed: Not needed
Fix: Available

What is CVE-2021-22175?

CVE-2021-22175 is a medium-severity server-side request forgery vulnerability in Gitlab Gitlab, published on 11 Jun 2021. An attacker can exploit it over the internet without logging in, with no action from the victim.

Official 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

Weakness: CWE-918

Which versions are affected by CVE-2021-22175?

1 open source package ship an affected version, including gitlab. It affects 1 product.

Package	Affected	Fixed in
`gitlab` Bitnami	From `10.5.0`	`13.6.7, 13.7.7, 13.8.4`

Products include Gitlab Gitlab.

How do I fix CVE-2021-22175?

Upgrade gitlab to a fixed version for your release line: 13.6.7, 13.7.7 or 13.8.4. US federal agencies must fix it by 11 Mar 2026.

Upgrade, and send outbound requests through an allow-list that blocks internal addresses. More about Server-side request forgery.

Is CVE-2021-22175 being exploited?

Yes. Attackers have exploited CVE-2021-22175 in the wild since at least 18 Feb 2026.

Public exploit code: 1 Nuclei template.

All Gitlab Gitlab vulnerabilities

Sources

Also known as BIT-gitlab-2021-22175, GHSA-4gm2-v7j4-74p8, UBUNTU-CVE-2021-22175.