How severe is CVE-2021-22175?

CVE-2021-22175 has a CVSS score of 9.8/10, rated CRITICAL. Immediate patching is strongly recommended.

Which packages are affected by CVE-2021-22175?

Affected package information for CVE-2021-22175 is not yet fully mapped. Check the official advisory links for details.

How do I fix CVE-2021-22175?

No fixed version has been published for CVE-2021-22175 yet. Monitor the advisory for updates, apply mitigations recommended by the vendor, and use O3 Security to track when a fix becomes available in your stack.

Is CVE-2021-22175 actively exploited in the wild?

No public exploit code has been indexed for CVE-2021-22175 yet. This does not mean the vulnerability cannot be exploited — absence of public exploits does not imply safety. Apply the recommended fix and use O3 Security to monitor your exposure.

What is the EPSS score for CVE-2021-22175?

CVE-2021-22175 has an EPSS (Exploit Prediction Scoring System) score of 80.0%, placing it in the 99th percentile of all CVEs. EPSS is maintained by FIRST.org and estimates the probability that a vulnerability will be exploited in the wild within the next 30 days. A score above 50% indicates significantly elevated exploitation risk — immediate patching is strongly recommended.

Is CVE-2021-22175 in the CISA Known Exploited Vulnerabilities catalog?

Yes. CVE-2021-22175 (GitLab Server-Side Request Forgery (SSRF) Vulnerability) was added to CISA's Known Exploited Vulnerabilities (KEV) catalog on 2026-02-18. CISA required all US federal civilian agencies to remediate this vulnerability by 2026-03-11. The required action was: Apply mitigations per vendor instructions, follow applicable BOD 22-01 guidance for cloud services, or discontinue use of the product if mitigations are unavailable. Being listed in the KEV catalog is the strongest possible confirmation of active exploitation — treat this as a critical priority.

Is there exploit tooling available for CVE-2021-22175?

A Nuclei detection template exists for CVE-2021-22175, meaning automated scanners can fingerprint it. Public exploit tooling significantly increases real-world risk — prioritize patching and ensure detection coverage. Exploit tooling should only ever be used in isolated, authorized testing environments.

When was CVE-2021-22175 published, and has it been updated?

CVE-2021-22175 was published on June 11, 2021 and was last updated on April 10, 2026. Advisory data evolves as severity scores, affected ranges, and exploit intelligence are revised — always check the latest version of the advisory before acting.

CVE-2021-22175: Server-Side Request Forgery (Critical 9.8)

EPSS Exploitation Probability

via FIRST.org ↗

80.0%probability of exploitation in next 30 days

Very High Risk99th percentile0.00%

EPSS (Exploit Prediction Scoring System) is a daily probability model maintained by FIRST.org. It estimates the likelihood a CVE will be exploited in production environments within the next 30 days, derived from real-world threat intelligence signals.

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

Frequently Asked Questions

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

O3 Security · Impact-Aware SCA

Is CVE-2021-22175 in your stack?

O3 detects CVE-2021-22175 across dependencies and uses function-level reachability to confirm whether the vulnerable code path is actually reachable — not just present. No false positives.

Scan my stack How O3 SCA works