CVE-2021-22175

GitLab server-side request forgery, confirmed exploited in the wild.

GitLab contains a server-side request forgery (SSRF) vulnerability when requests to the internal network for webhooks are enabled.

Check your domain free How we watch for this

53%chance of exploitation in the next 30 days (EPSS), 99th percentile

18 Febadded to CISA's Known Exploited Vulnerabilities list, 2026

11 Marfederal remediation deadline, already passed

Passedpast the deadline: patch now

CISA's name for it	GitLab Server-Side Request Forgery (SSRF) Vulnerability
Vendor and product	GitLab · GitLab
Type	server-side request forgery · CWE-918
Exploited	Confirmed by CISA listed 18 February 2026
Likelihood	one of the most likely to be exploited of every vulnerability tracked
Deadline	11 March 2026 · already passed
Used in ransomware	Not reported
Advisories	gitlab.com ↗ · nvd.nist.gov ↗

What to do

Three steps, in this order

Step 1

Apply the vendor's fix or mitigation; CISA lists only vulnerabilities seen exploited.

Step 2

If you cannot patch now, restrict network access to the affected product.

Step 3

Check for signs of compromise since the date it was added to the list.

CISA's 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.

Is it on your estate?

Know before someone else finds it

Threat Landscape Monitoring fingerprints the software your internet-facing hosts disclose and matches it, every day, against this list and the exploitation scores. When a new entry touches something you run, you are told once, with the host and the fix. The free plan covers one domain.

Start free with one domain Run the free domain check

Questions

CVE-2021-22175 in short

Is CVE-2021-22175 being exploited?

Yes. CISA added CVE-2021-22175 to its Known Exploited Vulnerabilities catalogue on 18 February 2026, which it does only on evidence of exploitation in the wild.

What is the CISA deadline for CVE-2021-22175?

US federal agencies must remediate it by 11 March 2026. Everyone else should treat that date as the latest safe point to patch an internet-facing system.

How likely is CVE-2021-22175 to be exploited in the next 30 days?

FIRST's Exploit Prediction Scoring System gives it 53%, the 99th percentile of every CVE it scores.

How do I fix CVE-2021-22175?

Apply the vendor's fix or mitigation; CISA lists only vulnerabilities seen exploited. If you cannot patch now, restrict network access to the affected product. Check for signs of compromise since the date it was added to the list.

Same vendor

Other GitLab vulnerabilities being exploited

CVE	Product	Type	Listed
CVE-2026-97229	Community Edition and Enterprise Edition	remote code execution	29 October 2026
CVE-2026-85706	Community Edition and Enterprise Edition	authentication bypass	11 September 2026
CVE-2021-39935	Community and Enterprise Editions	server-side request forgery	3 February 2026

Sources: CISA Known Exploited Vulnerabilities catalogue (released 10 November 2026) and FIRST EPSS. Page compiled automatically by SAK T.L.M, the threat-intelligence tool of SAK T.E.C, on 13 November 2026.