← gociux.comall exploited CVEs

Exploited vulnerability · CISA KEV

Is CVE-2021-22175 exploited? Yes: in CISA KEV since 18 Feb 2026

Gociux · GitLab · data: CISA KEV, CVE record, FIRST EPSS

Yes. CVE-2021-22175, GitLab Server-Side Request Forgery (SSRF) Vulnerability, is being exploited in the wild. CISA added it to its Known Exploited Vulnerabilities catalog on 18 Feb 2026, 1713 days after it was published. It affects GitLab. If you run it, CISA's required action is: Apply mitigations per vendor instructions, follow applicable BOD 22-01 guidance for cloud services, or discontinue use of the product if mitigations are unavailable.

exploitedYesCISA KEV · 18 Feb 2026
ransomwareNot knownno confirmed use
EPSStop 1%among the most likely CVEs to be exploited
severity6.8CVSS 3.1 · medium
US federal due11 Mar 2026BOD 22-01 deadline

What it is

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

VendorGitLab (6 exploited CVEs in KEV)
ProductGitLab
VulnerabilityGitLab Server-Side Request Forgery (SSRF) Vulnerability
WeaknessCWE-918
Published11 Jun 2021
Added to KEV18 Feb 2026
Reported by (CNA)GitLab

What to do

  1. Check whether you run it. Look for GitLab in your asset inventory, including appliances and cloud images. Stack check lists every exploited GitLab CVE at once.
  2. Apply the fix. Apply mitigations per vendor instructions, follow applicable BOD 22-01 guidance for cloud services, or discontinue use of the product if mitigations are unavailable.
  3. If you can't patch today, take the affected service off the internet or restrict who can reach it, and check its logs for signs of compromise since 11 Jun 2021.
  4. Get told next time. Email alerts when CISA adds a CVE for GitLab.

References

Questions

Is CVE-2021-22175 being exploited?

Yes. CISA added CVE-2021-22175 to the Known Exploited Vulnerabilities catalog on 18 Feb 2026, which means there is reliable evidence of exploitation in the wild.

Is CVE-2021-22175 used in ransomware attacks?

CISA does not list known ransomware use for it. That can change, and exploitation alone is reason to fix it first.

How do I fix CVE-2021-22175?

Apply mitigations per vendor instructions, follow applicable BOD 22-01 guidance for cloud services, or discontinue use of the product if mitigations are unavailable. Check GitLab's advisory for the fixed versions, and if you can't patch quickly, restrict access to the affected GitLab and watch it for signs of compromise.

Sources: CISA KEV (exploitation, ransomware use, required action, due date), the CVE record (publication date, CVSS, CNA), NVD and FIRST EPSS (live score). More: all KEV additions in February 2026 · GitLab scorecard · act-now radar.

Running GitLab in a regulated environment?

We check exposure across your estate, patch or mitigate with your team, and set up detection for what attackers do after exploiting it.

Get in touch →