dbcve.org
Actively exploited in the wild. This CVE is on the CISA Known Exploited Vulnerabilities list — treat remediation as urgent. Federal remediation due by 11 Mar 2026.
GitLabApplication

CVE-2021-22175

CRITICAL · 9.8 CVSS v3.1 Published 2021-06-11
Fix available
A fix is available. Upgrade to 13.6.7 / 13.7.7 or later.
See remediation →
100/100
Remediation priority · Urgent
In the wild High EPSS Public exploit Remotely reachable No privileges Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
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

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

This is a server-side request forgery (SSRF) vulnerability in GitLab's webhook functionality. When requests to internal networks for webhooks are enabled, an unauthenticated attacker can cause the GitLab server to make arbitrary requests to internal network resources, potentially accessing internal services, bypassing network segmentation, and enumerating internal infrastructure.

MitigationUpgrade to the patched GitLab version. If immediate patching is not possible, disable webhook requests to internal networks via GitLab administrative settings and implement network-level filtering to block SSRF attempts.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
GitLabApplication
Affected:>= 10.5.0, < 13.6.7>= 13.7.0, < 13.7.7>= 13.8.0, < 13.8.4

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
None
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Identify GitLab version
    Run `sudo gitlab-rake gitlab:env:info` or check the GitLab admin area under /admin/application_settings or look at /opt/gitlab/version-manifest.txt
    Affected if The installed version falls within: 10.5.0 to 13.6.6, 13.7.0 to 13.7.6, or 13.8.0 to 13.8.3
  2. Verify webhook functionality is accessible
    Check if webhooks can be created by navigating to Project Settings > Webhooks (or API endpoint /api/v4/hooks) - requires at least Maintainer access
    Affected if Webhooks functionality is enabled and accessible to attackers
  3. Confirm internal network requests setting for webhooks
    Navigate to GitLab Admin Area > Settings > Network > Outbound requests > check 'Allow requests to the internal network' for webhooks (or check via API: GET /api/v4/application/settings)
    Affected if The setting 'Allow requests to the internal network from webhooks and services' is enabled (value: true)
  4. Identify configured webhooks
    List project webhooks via API: GET /api/v4/projects/:id/hooks or check Project Settings > Webhooks page
    Affected if Any webhooks exist that could be manipulated to trigger SSRF to internal resources

You are affected if running an affected GitLab version (10.5.0-13.6.6, 13.7.0-13.7.6, or 13.8.0-13.8.3) AND webhooks are accessible AND the internal network requests setting for webhooks is enabled.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Upgrade available Upgrade to 13.6.7 / 13.7.7 / 13.8.4 or later
Fixed in 13.6.713.7.713.8.4
Interim mitigation

Upgrade to the patched GitLab version. If immediate patching is not possible, disable webhook requests to internal networks via GitLab administrative settings and implement network-level filtering to block SSRF attempts.

Recommended fix High confidence

13.8.4 or later

  1. Upgrade GitLab to version 13.8.4 or later (recommended), or at minimum to the appropriate fixed version for your current branch: 13.6.7, 13.7.7, or 13.8.4
  2. If upgrading to a later major version (e.g., 13.10+, 14.x, 15.x), review the GitLab upgrade documentation for any required pre-upgrade steps
  3. Back up your GitLab instance before performing the upgrade
  4. After upgrading, verify the webhook functionality works as expected
  5. Consider reviewing webhook settings to ensure internal network requests are properly restricted if not needed
Caveat Major version upgrades (e.g., 13.x to 14.x) may require additional migration steps and have breaking changes; review release notes before upgrading across major versions

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in GitLab Exploited in the wild — priority engagement
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing6.0 h
  • Review / QA2.0 h
20.0 hours of engineering $3,500
Get it fixed fast

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $5,600.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2021-22175 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2021-22175 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data