Skip to content
WatchlistHigh

CVE-2018-19571Gitlab SSRF

GitLab CE/EE, versions 8.18 up to 11.x before 11.3.11, 11.4 before 11.4.8, and 11.5 before 11.5.1, are vulnerable to an SSRF vulnerability in webhooks.

Published Jul 10, 2019 · Updated Aug 27, 2026

Key Facts

Patch immediately
  • CVE-2018-19571 is a high-severity vulnerability (CVSS 7.7 v3.1) affecting Gitlab.
  • It is not listed in any known-exploited vulnerabilities catalog. Public exploit code is available.
  • EPSS estimates a 32% probability of exploitation in the next 30 days.
  • Fixed versions are available, including Gitlab 11.3.11+dfsg-1, Gitlab 11.3.11.
  • Brandefense priority: patch immediately, because public exploit code exists for a high-severity flaw.

Scores

CVSS v3.1

7.7

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:N/A:N

EPSS (30-day exploit likelihood)

32%

Higher than 98.3% of all scored CVEs

Exploit maturity

Proof of concept

ATLAS score

46/100

Publication score, see How it works

Exploitation Verdict

KEV listed

Not listed

Federal due date

None

No federal due date

Ransomware use

Not reported

Attributed actors

None named

Exploit & Defence Guidance

Exploit maturity

Proof of concept

Public exploit code

2

Proof-of-concept links

In-the-wild evidence

0

Reports of active use

Description

GitLab CE/EE, versions 8.18 up to 11.x before 11.3.11, 11.4 before 11.4.8, and 11.5 before 11.5.1, are vulnerable to an SSRF vulnerability in webhooks.

Affected Products

3 affected entries in total
ProductAffected versionsFixed in
GitlabGitlabSee advisory11.3.11

Patched Releases

Gitlab

11.3.11+dfsg-1, 11.3.11

Timeline

  1. Publicly disclosed

    Jul 10, 2019

  2. Last updated

    Aug 27, 2026

Weakness Type

  • CWE-918 Server-Side Request Forgery (SSRF)

FAQ

Common Questions.

Is CVE-2018-19571 On Your Attack Surface?

Brandefense matches it against the products discovered on your perimeter and opens a finding the day a CVE like this is listed.

Request A Demo

Figures as of Oct 19, 2026. Compiled by Brandefense technologies from public vulnerability catalogs; scoring as described in How it works.

To report an error, contact Brandefense.