CVE Intelligence
CISA KEV Critical SSRF exploit reference

CVE-2021-22175 — GitLab Server-Side Request Forgery (SSRF) Vulnerability

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

Published Jun 11, 2021 · Updated Oct 13, 2026 · Sources: CISA Known Exploited Vulnerabilities, NIST National Vulnerability Database, CVE Program (cve.org) e CISA ADP, GitHub Security Advisories · CNA: GitLab

Who exploits it and how urgent it is

A 0–100 score combining confirmed exploitation, ransomware and APT use, public exploits, EPSS and severity.

CISA KEV · Feb 18, 2026 Detection templates (Nuclei) · 1
How the score was calculated
  • Confirmed exploitation (CISA KEV)+35
  • Public exploit/PoC (nuclei)+4
  • EPSS 53.4% (30-day exploitation probability)+15
  • Technical severity (critical)+10

The score orders the patch queue; it does not replace your asset context (internet exposure, criticality, compensating controls).

Triage

Is it exploited, how likely is exploitation, what does it touch, and how severe do the sources call it.

Exploitation
Confirmed
CISA KEV, listed Feb 18, 2026
EPSS FIRST
53.37%
ahead of 99% of scored CVEs · Oct 14, 2026
Affects
Gitlab
Gitlab
CVSS base
9.8
Critical · 4 source(s)

CISA SSVC assessment CISA

Three decision points CISA publishes for the CVEs it assesses (SSVC 2.0.3). A stakeholder decision, not a severity score.

Exploitation
Active
none · proof-of-concept · active
Automatable
No
can an attacker script the kill-chain steps
Technical impact
Total
partial · total control of the vulnerable component

Remediation

Fixes and mitigations documented by the sources — linked to the original advisory.

No fix documented by the sources we poll. That does not mean none exists: check the vendor advisory.

CISA required action CISA

Apply mitigations per vendor instructions, follow applicable BOD 22-01 guidance for cloud services, or discontinue use of the product if mitigations are unavailable.

US federal deadline: Mar 11, 2026 — passed 218 day(s) ago

First 24 hours

Ordered from the record’s own fields — exposure first, because you cannot patch what you have not found. A rule-generated starting point.

  1. Identify exposed assets running the affected vendor/product/version combinations (Gitlab Gitlab).
  2. Treat as emergency remediation: the CVE is in CISA KEV (confirmed exploitation).
  3. The attack is network-based and needs no privileges: restrict exposure (ACLs, VPN, WAF) until patched.
  4. No fix documented in the sources: reduce exposure and monitor the vendor advisory.
  5. EPSS ahead of 99% of scored CVEs: prioritize it in the patch queue.
  6. Search available logs for exploit probes matching the vulnerability class (ssrf), errors and authentication anomalies.

Affected scope

Vendor, product and versions as the sources word them.

VendorProductVersionsStatusSource
Gitlab Gitlab ≥ 10.5.0 and < 13.6.7≥ 13.7.0 and < 13.7.7≥ 13.8.0 and < 13.8.4 Vulnerable NIST National Vulnerability Database
Gitlab Gitlab version >=10.5, <13.6.7version >=13.7, <13.7.7version >=13.8, <13.8.4 Vulnerable CVE Program (cve.org) e CISA ADP

Attack characteristics

The CVSS vector, decoded. It describes the attack, not your exposure to it.

Attack vector
Network
Attack complexity
Low
Privileges required
None
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

Every base score collected

Sources score independently and may disagree; each row says who scored it and under which version.

ScoreVersionSeverityExpl.ImpactScored by
9.8 CVSS 3.1 Critical 3.9 5.9 nvd@nist.gov via NIST National Vulnerability Database
9.8 CVSS 3.1 Critical — — GitHub, Inc. via GitHub Security Advisories
6.8 CVSS 3.1 Medium 2.2 4.0 cve@gitlab.com via NIST National Vulnerability Database
6.8 CVSS 3.1 Medium — — GitLab via CVE Program (cve.org) e CISA ADP
6.8 CVSS 2.0 Medium 8.6 6.4 nvd@nist.gov via NIST National Vulnerability Database
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H (score shown at the top: nvd@nist.gov)
Scoring entities (NIST, CNA, ADP) score independently; each score is shown with its origin. For prioritization we use 9.8 (NVD (NIST)) as a conservative provisional reference — not a definitive official score.

Weakness MITRE

Weakness class according to MITRE’s CWE catalog.

CWE-918 · Server-Side Request Forgery (SSRF)

Other CVEs with this weakness →

CISA KEV details CISA

CISA lists a CVE once it has evidence of exploitation against real targets.

Listed
Feb 18, 2026
Federal deadline
Mar 11, 2026
passed 218 day(s) ago
Ransomware use
Unknown

CISA records ransomware use only for campaigns it has confirmed, so “Unknown” means unrecorded, not ruled out. The deadline binds US federal agencies; for everyone else it is a reference date.

Public exploits, PoCs and detection templates

Public code that demonstrates or tests the flaw raises the odds of mass exploitation — and Nuclei templates help find vulnerable assets in your environment.

Detection templates (Nuclei)

Warning: public PoCs are sometimes disguised malware. Use them only for authorized testing in an isolated environment. This portal does not host exploit code — it only points to the sources.

EPSS over time FIRST

Oct 12, 2026 → Oct 14, 2026 · 3 reading(s) · max 53.37%

Detection

Read off the CVSS vector and the weakness class. Starting points, not tested rules.

  • Prioritize edge telemetry for the network-reachable component (proxy, WAF, IDS/IPS).
  • Monitor outbound requests from the server to internal IPs and cloud metadata endpoints.
  • Hunt retroactively in logs from before Feb 18, 2026 (KEV listing): exploitation may have started earlier.
web/proxy/WAF logsnetwork IDS/IPSegress traffic

Timeline

What happened to this CVE, newest first.

  • 2026
  • Affected products added · gitlab/gitlab
    Oct 13, 2026 · CVE Program (cve.org) e CISA ADP
  • SSVC assessment updated
    Oct 13, 2026 · CVE Program (cve.org) e CISA ADP
  • Record published
    Oct 13, 2026
  • Affected products added · gitlab/gitlab
    Oct 13, 2026 · NIST National Vulnerability Database
  • CVSS changed · 9.8
    Oct 13, 2026 · NIST National Vulnerability Database
  • Source status changed · → Analyzed
    Oct 13, 2026 · NIST National Vulnerability Database
  • Added to CISA KEV (detected)
    Oct 13, 2026 · CISA Known Exploited Vulnerabilities
  • Record created in this database
    Oct 13, 2026 · CISA Known Exploited Vulnerabilities
  • Added to CISA KEV catalog
    Feb 17, 2026 · CISA
  • 2021
  • CVE published
    Jun 11, 2021 · GitLab

Source activity

Repeated readings are counted rather than listed.

  • 2× References added · Oct 13, 2026 – Oct 13, 2026
  • 1× Official description updated · Oct 13, 2026 – Oct 13, 2026

References

6 on the record

Elsewhere on this site

Gitlab
every CVE for this vendor
2026-02
what else CISA listed that month
SSRF
same class
CWE-918
other pages naming this weakness

Related CVEs (same products)

  • CVE-2026-97229 Integer Overflow or Wraparound in GitLab 2d
  • CVE-2026-84284 Incorrect Authorization in GitLab 2d
  • CVE-2026-92528 Incorrect Authorization in GitLab 2d
  • CVE-2026-9268 Incorrect Authorization in GitLab 2d
  • CVE-2026-96893 Improper Neutralization of Input Used for LLM Prompting in GitLab 2d
  • CVE-2026-92883 Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting') in GitLab 2d

Not in any source we poll

Listed rather than left blank: an empty field and an unmeasured one look identical on screen, and only one is a reason to look elsewhere.

  • No fixed version, patch or mitigation documented.
  • No confirmed IOCs, IP addresses, domains, file hashes, or malware artifacts supplied.
  • No organization-specific asset inventory, compensating-control status, or patch deployment evidence supplied.
  • No exploit packet captures, log samples, or incident case IDs supplied.

Answered from this record

Text assembled only from the fields above — no additional claims.

What should defenders know first?

CVE-2021-22175 is "GitLab Server-Side Request Forgery (SSRF) Vulnerability", rated Critical. It affects Gitlab (Gitlab); versions are in the scope table. It is in CISA KEV: there is evidence of real-world exploitation. CVSS 9.8 describes technical severity. EPSS 53.37% estimates the probability of exploitation in 30 days; neither replaces your asset context. First verify whether exposed or business-critical assets run the affected versions, apply vendor fixes or mitigations, and preserve logs for review.

Comments

Moderated technical discussion. Read the community guidelines.

No comments yet.

Sign in or create an account to comment and suggest corrections.