An information exposure vulnerability exists in gitlab.com <v12.3.2, <v12.2.6, and <v12.1.10 when using the blocking merge request feature,…

published 2019-12-18 6 y ago modified 2026-06-17 4 mo ago also EUVD-2019-6548

cvss: 6.5; version 3.1, NVD
cisa kev: Not listed; not in CISA's catalog
epss: 1.1%; EPSS 1.1% chance of exploitation in 30 days, percentile 66%
public exploits: 0; none known

An information exposure vulnerability exists in gitlab.com <v12.3.2, <v12.2.6, and <v12.1.10 when using the blocking merge request feature, it was possible for an unauthenticated user to see the head pipeline data of a public project even though pipeline visibility was restricted.

Patch / fix

fixed in 1

gitlab gitlab 12.1.10, 12.2.6, 12.3.2

Exploit prediction

1.14% chance of exploitation in the next 30 days, higher than 66% of all scored CVEs (FIRST EPSS, 2026-11-08).

Exploits and checks

hackerone.com https://hackerone.com/reports/667408 referenced PoC, tagged "exploit" by a source, unverified

CVSS scores

assigned by	version	score	vector
NVD	3.1	6.5	CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N
NVD	2.0	4.0	AV:N/AC:L/Au:S/C:P/I:N/A:N

Affected products

n/a gitlab.com

Classification

Weakness

CWE-201 Insertion of Sensitive Information Into Sent Data
CWE-200 Exposure of Sensitive Information to an Unauthorized Actor

Technology feeds

GitLab rss critical rss

References

hackerone.com /reports/667408
exploit, third-party-advisory

Sources

CVE List CVE-2019-15580
NVD CVE-2019-15580

Fencer Vulns keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.

Summary