CVE-2021-22175
Server-side request forgery lets unauthenticated attackers reach GitLab's internal network
A server-side request forgery (SSRF) flaw in GitLab lets an unauthenticated attacker make the GitLab server send requests to internal network resources. This is possible when requests to internal networks for webhooks are enabled, and it affects even GitLab instances where registration is disabled. GitLab versions from 10.5 are affected; CISA lists the vulnerability as actively exploited, and no fixed version is given in the records.
GitLab · Updated 30 Oct · From the public records
Am I affected?
The records do not list fixed versions yet. Check the vendor's advisory below.
What to do
- Treat this as urgent because CISA has confirmed active exploitation.
- No fixed version or workaround is provided in the records, so monitor GitLab's advisory and apply any update as soon as it is released.
- If you are a US federal agency, remediate by CISA's deadline of 2026-03-11.
What happened
- 18 FebCISA added the GitLab SSRF vulnerability to its Known Exploited Vulnerabilities catalog, requiring US federal agencies to fix it by 2026-03-11.
- 30 OctBleepingComputer reported CISA saying a max severity GitLab flaw is now exploited in the wild.
The record
| CVE | What it is | Severity | CISA listed | Exploit chance, 30 days |
|---|---|---|---|---|
| CVE-2021-22175 | GitLab Server-Side Request Forgery (SSRF) Vulnerability | medium 6.8 | 18 Feb | 53% |
Our reporting
We have not reported on it. It is here because CISA added it to its list of flaws under attack.