Your RSA-2048 keys break in 2030. Find every one of them before attackers do.
🛡️
CISA KEV · ACTIVELY EXPLOITED
CRITICAL severity

CVE-2021-22175 — gitlab

CRITICAL

CVE-2021-22175 is a critical-severity (CVSS 9.8) Server-Side Request Forgery (SSRF) vulnerability. It is in CISA's Known Exploited Vulnerabilities catalog (added 2026-02-18) — treat it as actively exploited and patch now. A fix is available — see the affected versions and patch details below.

Also known asBIT-gitlab-2021-22175
Published
Updated
Affected
1 product
Patched
See advisory
Exploits
None indexed
Exploitation data as of Oct 23, 2026 · OSV.dev, NVD, CISA KEV, FIRST.org (EPSS)

Exploitation Status

Actively exploited in the wild

  • Confirmed by CISA's Known Exploited Vulnerabilities catalog on 2026-02-18. Federal agencies were required to remediate by 2026-03-11.
  • A successful exploit gives an attacker total control of the affected component, not partial access.

Exploitation and automatability from CISA (KEV catalog and SSVC triage) for CVE-2021-22175.

EPSS Exploitation Probability

via FIRST.org ↗
53.4%probability of exploitation in next 30 days
High Risk0.00%
Lower risk than most CVEs99th percentile — riskier than 99% of all scored CVEsHighest risk
49.5%56.4%63.2%70.0%66.2%53.4%53.4%Apr 26Aug 26Oct 26

Probability of exploitation in the next 30 days, from FIRST.org EPSS.

How urgent is this, really

CVE-2021-22175 by exploitation likelihood (EPSS) against impact (CVSS). In the shaded patch-first corner (EPSS 50%+, CVSS 7.0+).

Where this sits among everything scored

Of 395,249 CVEs with a current EPSS score, this one falls in the 50–90% band (highlighted). Counts from FIRST.org, log-scaled.

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

Affected Products

1 product · 6 configurations
Application
gitlabgitlab
≥ 13.8.0 && < 13.8.4
range

Detection & mitigation playbook

Vulnerability
  1. Detect

    Identify every host running the affected component and compare the installed build against the fixed version below — for source-built or distro-packaged software the version string, not a lockfile, is the source of truth (`dpkg -l`, `rpm -q`, or the binary's own `--version`).

  2. Fix

    Upgrade the affected component to the fixed release for CVE-2021-22175, or apply your distribution's backported patch — distro builds are often patched at an older version number, so check your vendor's advisory rather than the upstream version alone.

  3. Workarounds

    Restrict outbound requests from the affected component to an allowlist of hosts, block access to link-local and internal address ranges at the network layer, and require authentication on internal services so a forged request cannot reach them unauthenticated.

How to detect CVE-2021-22175

A community-maintained Nuclei template exists for this CVE. You can scan for it directly:

nuclei -id cve-2021-22175 -u https://target
Template
GitLab CI Lint API - Server-Side Request Forgery
Severity
high
Impact
Unauthenticated attackers can perform arbitrary requests on internal network, potentially leading to information disclosure or internal network compromise.
Remediation
Update to the latest version of GitLab where the vulnerability is fixed.

Template by ProjectDiscovery nuclei-templates (0x_Akoko), MIT licensed. View the full template. Scan only systems you are authorised to test.

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 dependencies?

Find it across , including transitive dependencies.

CVE-2021-22175: gitlab SSRF (Critical 9.8, KEV)