GitLab · GitLab · GitLab Server-Side Request Forgery (SSRF) Vulnerability
Verdict
Patch first · actively exploited, reachable from the internet without credentials, and in the top 5% of CVEs by near-term exploitation probability
Added to CISA KEV 2026-02-18 · exploited in the wild for 222 days
CVSS 6.8 MEDIUM. The score is a summary; these three components are the part that decides whether something scanning the internet can use it.
| Attack vector | networkreachable over the network, with no local access needed |
|---|---|
| Privileges required | noneneeds no credentials at all |
| User interaction | nonecan be triggered with nobody interacting with the page or request |
| Base vector | CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:C/C:H/I:N/A:N |
| Weakness | CWE-918 |
This describes the vulnerability. It says nothing about whether your systems run it.
EPSS puts the probability of exploitation in the next 30 days at 0.5337, which places it in the top 5% of all tracked CVEs. The percentile is the more useful half: 0.18 in absolute terms sounds low until you know most of the internet-facing software in the world scores under that.
| EPSS probability | 0.5337 |
|---|---|
| Percentile | 0.990 — top 5% |
| Added to KEV | 2026-02-18 |
|---|---|
| Days exploited | 222 |
| Federal remediation due | not set |
| Ransomware use | no known ransomware campaign use |
Apply mitigations per vendor instructions, follow applicable BOD 22-01 guidance for cloud services, or discontinue use of the product if mitigations are unavailable.
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
Web application penetration testing · API security testing · every service