Skip to main content
Apexward Pulse
Type Vulnerability

GitLab

GitLab Server-side Request Forgery (SSRF) Vulnerability

1 sourceCVE-2021-22175

At a glance

High
Suggested 24-hour window, counted from the last update
ActiveConfirmed in-the-wild exploitation
Evidence-weighted, not popularity
Signal

Actively exploited in the wild — prioritise confirming exposure.

Why High

High rather than Critical: exposure is scored at a default because we cannot see your systems or suppliers. If you run or depend on GitLab Runner, treat it as Critical.

Briefing

  • Do not treat uncorroborated claims as confirmed breaches.

Questions to ask IT

  • Do we run GitLab Runner, and which versions?
  • Is any of it reachable from the internet?
  • Have we checked whether it has already been used against us?
  • If it is still not patched, what mitigation is in place, and what is holding the fix up?

Next steps

  1. Confirm exposure, mitigation status and any service interruption risk.

Summary

  • GitLab contains a server-side request forgery (SSRF) vulnerability when requests to the internal network for webhooks are enabled.
  • CVE-2021-22175 is listed in known-exploited catalogue (exploitation in the wild)
  • Authoritative catalogues report active exploitation of this vulnerability.

Why this matters in the UK

  • Known-exploited catalogue reports exploitation in the wild

Products and services involved

Pulse

Last checked 4d ago · Recheck overdue since 5 Nov 2026, 22:02 UK time · 3 quiet checks collapsed

Signal
4 Nov 2026, 22:02 UK time · 4d ago

in the next 30 days first recorded at 53.4% (elevated likelihood signal, not confirmed exploitation).

Elevated — confirm exposure; this is a probability signal, not confirmed exploitation.

EscalationDe-escalationCritical / liveWhat these mean
Drag to pan · Ctrl / ⌘ + scroll or pinch to zoom6 events

2 quiet checks hidden.

Sources

How we know

Statements extracted from sources. Higher confidence means stronger corroboration.

  • ConfirmedHeadline90% confidence

    GitLab Server-Side Request Forgery (SSRF) Vulnerability

  • ConfirmedSummary fact75% confidence

    GitLab contains a server-side request forgery (SSRF) vulnerability when requests to the internal network for webhooks are enabled. Affects GitLab GitLab. Known ransomware campaign use: Unknown. 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.

  • ConfirmedCVE identifier95% confidence

    Event involves CVE-2021-22175

  • ConfirmedKnown-exploited catalogue98% confidence

    CVE-2021-22175 is listed in known-exploited catalogue (exploitation in the wild)