How serious is CVE-2021-22175?

This vulnerability has a CVSS score of 9.8 out of 10, classified as CRITICAL severity. Proof-of-concept exploit code is publicly available, making this an active threat.

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

Yes, proof-of-concept exploit code for CVE-2021-22175 is publicly available on GitHub and security research platforms. This increases the risk of active exploitation.

Which products are affected by CVE-2021-22175?

CVE-2021-22175 affects gitlab gitlab. Check the full CVE details for specific version information.

How do I fix CVE-2021-22175?

To remediate CVE-2021-22175, check for security patches from gitlab. Apply all available updates and security patches. If no patch is available, implement recommended workarounds or security controls to mitigate the risk.

CVE-2021-22175

Critical

|9.8

Exploit Available

Plain English Summary

AI-powered analysis for quick understanding

This vulnerability allows an attacker to send malicious requests to internal services within a GitLab instance, potentially exposing sensitive data or causing disruptions. It can be exploited by anyone, even if they are not logged in, as long as the GitLab instance has webhooks enabled and is running a version from 10.5 onward.

Technical 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

CVSS Vector Analysis

Attack VectorNetwork

Attack ComplexityLow

Privileges RequiredNone

User InteractionNone

Confidentiality ImpactHigh

Integrity ImpactHigh

Availability ImpactHigh

ScopeUnchanged

Vector String

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

Exploit Resources

Search for proof-of-concept code and exploit modules

GitHub Search Exploit-DB Nuclei Templates Metasploit Vulners

Official References

NIST NVD

Est. Bounty

$13,000($5K-$15K)

Vendor Response

Grade FPatched in 1713 days

Quick Information

Published

Jun 11, 2021

almost 5 years ago

Last Modified

Feb 18, 2026

about 2 months ago

Vendor

gitlab

Product

gitlab

Related Vulnerabilities

CVE-2026-0602Medium

An attacker with an authenticated account could potentially access sensitive metadata from private issues, merge requests, and other project elements due to a flaw in how GitLab handles snippets. This issue affects specific versions of GitLab and occurs under certain conditions when rendering snippets.

CVE-2025-14513High

An attacker could exploit a flaw in GitLab's API to send specially crafted data that causes the system to crash, leading to a denial of service. This vulnerability affects specific versions of GitLab and can be triggered by anyone without needing to log in.

CVE-2025-13929High

This vulnerability allows an attacker to crash the GitLab service by sending specially crafted requests to certain repository archive endpoints, effectively causing a denial of service. It affects specific versions of GitLab, and the attacker does not need to be logged in to exploit it.

CVE-2025-13690Medium

This vulnerability allows an authenticated user to crash the GitLab server, leading to a denial of service, by sending specially crafted webhook header names. It affects specific versions of GitLab and requires the attacker to have access to an account on the system.

CVE-2025-12704Medium

An attacker could access sensitive Virtual Registry data from groups they don't belong to if they were already logged into GitLab, due to a flaw in the system's authorization checks. This issue affects specific versions of GitLab and requires the attacker to be an authenticated user.