Skip to content
VulniPulse
Advisory severityMedium6.8GitLab Exploited CISA KEV

Medium [CVE-2021-22175] 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

This medium-severity GitLab advisory covers CVE-2021-22175 affecting GitLab.

Aggregated and source-linked by VulniPulse. Data sources, validation and limitations.

CVE-2021-22175 Source published Source updated

VulniPulse record published

Affected products & platforms
GitLabUnclassified
Open source advisory

Android app · Google Play

Monitor future GitLab CVEs from your phone.

Choose a whole vendor or a precise platform, then receive matching security advisories by phone notification, email, or both. Coverage follows 34 official vendor sources and 160+ reviewed platform categories.

Matching phone alertsOptional email delivery

Summary

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

CISA Known Exploited Vulnerability

Listed:
Feb 18, 2026 · federal remediation due Mar 11, 2026
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.
Ransomware use:
Unknown

KEV is a prioritization signal from CISA — remediation detail still comes from the vendor advisory.

Affected versions
  • GitLab >=10.5, <13.6.7
  • GitLab >=13.7, <13.7.7
  • GitLab >=13.8, <13.8.4

Official advisory · high-confidence parse· fetched 13 days ago·verify at source

Fixed versions

No fixed release is recorded yet. That does not prove no patch exists — confirm against the vendor advisory.

Official advisory · high-confidence parse· fetched 13 days ago·verify at source

Mitigation

The source record does not include mitigation steps. That is not a statement that no fix exists — read the vendor advisory below for the authoritative guidance.

Official advisory · high-confidence parse· fetched 13 days ago·verify at source

Discussion(0)

No comments yet. Share field notes, upgrade gotchas, or questions — verify against the vendor advisory before acting on community advice.

Sign in to join the discussion.