CVE-2021-22175
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
do firstApply mitigations per vendor instructions, follow applicable BOD 22-01 guidance for cloud services, or discontinue use of the product if mitigations are unavailable.
Can a WAF block it? No. The vulnerability involves server-side request forgery via HTTP requests to internal network webhooks, which appear as normal requests and do not contain unusual patterns that a WAF could reliably detect without blocking legitimate traffic.
Also consider: egress filter · IMDSv2
Based on an AI reading of the CVE description, and no vendor rule found yet. We check Cloudflare, AWS, Google Cloud Armor and Azure; for Akamai, Imperva, Fastly, F5, ask your vendor.
Is CVE-2021-22175 being exploited?
Yes. CVE-2021-22175 appears in CISA's Known Exploited Vulnerabilities catalog, which means exploitation in the wild has been confirmed and reported. Treat it as active rather than theoretical, and patch it ahead of higher-scoring vulnerabilities that carry no exploitation evidence.
How severe is CVE-2021-22175?
CVE-2021-22175 is rated Medium with a CVSS score of 6.8. Severity describes how bad exploitation would be, not how likely it is: pair it with exploitation evidence before deciding what to patch first.
Is there a patch for CVE-2021-22175?
Yes. A fix has been recorded for CVE-2021-22175. The vendor advisory is the authority on the exact fixed version — apply it from there rather than from a summary.
What does CVE-2021-22175 affect?
CVE-2021-22175 affects gitlab:gitlab. Confirm the exact affected versions against the vendor advisory before deciding you are exposed.
Exploitation status reflects CISA's KEV catalog as we last synced it. Check the catalog directly.
- affected>= 10.5 and < 13.6.7
- affected>= 13.7 and < 13.7.7
- affected>= 13.8 and < 13.8.4
As published in the CVE Program record. A version outside these ranges is not a statement that it is unaffected — vendors sometimes understate a range, and distribution-backported builds carry upstream numbers that do not reflect what was patched into them.
public exploits
Detection templates only, no public exploit found: 1 Nuclei template
- GitLab CI Lint API - Server-Side Request Forgery · detection template · high
Listed so you can judge urgency, not as a recommendation to run anything. GitHub “proofs of concept” are unvetted: some are fake or carry malware. Exploit-DB marks the entries its staff verified.
cisa ssvc
- exploitation
- active
- automatable
- no
- technical impact
- total
Assessed by CISA 19 Feb 2026 (SSVC 2.0.3).
timeline
- 11 Jun 2021Published
- 18 Feb 2026Added to CISA KEV (exploited in the wild) · 1,712 days (about 5 years) later
- 19 Feb 2026CISA SSVC assessment: exploitation active · 1 day later
- 11 Mar 2026CISA remediation due date (US federal agencies) · 20 days later
- 1 Oct 2026CVE record last updated · 205 days (about 7 months) later
- 2 Nov 2026Analysed by vulneraibility.com · 32 days later
- Linkgitlab.com /gitlab-org/gitlab/-/issues/294178
- Linkhackerone.com /reports/1059596
- Linkgitlab.com /gitlab-org/cves/-/blob/master/2021/CVE-2021-22175.json
- Linkcisa.gov /known-exploited-vulnerabilities-catalog?field_cve=CVE-2021-22175
sources
- CVE List (CVE.org): description, affected versions, references; CVE Terms of Use
- NVD: CVSS and CPE data
- CISA KEV catalog: exploitation, date added, due date
- CISA Vulnrichment (ADP): SSVC decision points
- FIRST EPSS: exploit probability and percentile
- Nuclei templates: detection templates
- Summary, impact and triage tags: written by our AI analysis pipeline from the sources above. Check them against the sources.