Quick answer
Yes. CVE-2021-22175 in GitLab GitLab is being exploited by attackers: CISA added it to its Known Exploited Vulnerabilities catalogue on 18 February 2026. If you run GitLab, apply the vendor's fix now and check for signs of compromise.
What is CVE-2021-22175?
GitLab Server-Side Request Forgery (SSRF) Vulnerability. GitLab contains a server-side request forgery (SSRF) vulnerability when requests to the internal network for webhooks are enabled.
Description from the CISA Known Exploited Vulnerabilities catalogue.
What kind of flaw is it?
The server can be made to send requests on the attacker's behalf, often reaching internal systems or cloud credentials.
Other exploited server-side request forgery (ssrf) How it worksWhy it matters
Source code platforms, build servers and collaboration tools hold code, secrets and credentials. Exploiting them can lead to supply chain attacks on everyone who uses your software.
Higher than 99% of all scored vulnerabilities.
Am I affected? How to check | What to do now |
|---|---|
1Confirm whether you self-host the affected tool. | 1Apply the vendor fix. |
2Check versions against the advisory and whether the instance is internet-facing. | 2Rotate tokens and secrets stored in the platform if exposure is possible. |
3Review audit logs for new tokens, accounts or changes to pipelines. | 3Restrict access to internal networks or SSO-protected access. |
Am I affected? How to check
- 1Confirm whether you self-host the affected tool.
- 2Check versions against the advisory and whether the instance is internet-facing.
- 3Review audit logs for new tokens, accounts or changes to pipelines.
What to do now
- 1Apply the vendor fix.
- 2Rotate tokens and secrets stored in the platform if exposure is possible.
- 3Restrict access to internal networks or SSO-protected access.
CISA required action: Apply mitigations per vendor instructions, follow applicable BOD 22-01 guidance for cloud services, or discontinue use of the product if mitigations are unavailable.
How fast to patch
Under the Essential Eight, patches for internet-facing services should be applied within 48 hours when a working exploit exists, and higher maturity levels apply the same 48-hour target to applications such as browsers and office software. A vulnerability in this catalogue has, by definition, been exploited in the wild, so treat it as the 48-hour case.
In the news
More in the daily briefing.
Common questions
Is CVE-2021-22175 being exploited?
Yes. It is listed in CISA's Known Exploited Vulnerabilities catalogue, which only includes vulnerabilities with confirmed exploitation in the wild. It was added on 18 February 2026.
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 the vendor advisory for fixed versions, and if the system was exposed while unpatched, investigate it for signs of compromise.
Is my GitLab GitLab affected?
Check your installed version against the vendor advisory linked on this page. If the affected component is reachable from the internet and unpatched, assume it is at risk and act immediately.