On 2026-02-18, CISA added CVE-2021-22175 (GitLab GitLab) to its Known Exploited Vulnerabilities (KEV) catalog [2]. The vulnerability is listed in the catalog as "GitLab Server-Side Request Forgery (SSRF) Vulnerability" [2]. CISA requires remediation in accordance with the listed vendor mitigation guidance; see the original text in the body for specific requirements [2].
Backfill: this event became public on Feb 18, 2026 and we added it on Nov 10, 2026. It is not a new event.
CISA Adds GitLab GitLab Vulnerability CVE-2021-22175 to Known Exploited Vulnerabilities Catalog
1 min read
- Disclosed
- Feb 18, 2026
- Published
- Nov 10, 2026
- Last updated
- Nov 8, 2026
- CVSS basis
- Our assessment
- 53.4%, higher than 99% of CVEs
- Exploitation and patch status
- ExploitedKEV
- Attack vector
- Vulnerability status
- Actor type
- Motivation
On this page
30-second summary
What happened
Who is affected
Industries mainly affected: Government, Cross-industry
What to do nowOur advice
CISA requires remediation in accordance with the listed vendor mitigation guidance; see the original text in the body for specific requirements [2].
Timeline
Technical details
CISA KEV Listing Record
CISA added CVE-2021-22175 (GitLab GitLab) to the Known Exploited Vulnerabilities () catalog on 2026-02-18 [2].
Original Technical Description
GitLab contains a server-side request forgery (SSRF) vulnerability when requests to the internal network for webhooks are enabled. [2]
Official 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. [2]
Individual Vulnerability Record
The U.S. National Vulnerability Database (NVD) provides an independent vulnerability record and description for CVE-2021-22175 [1].
References
Official / primary3
- [1]
“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”
- [2]
This site aggregates public information and is not security consulting advice. Test remediation steps before applying.