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 6 y ago 2019-12-18 · modified 4 mo ago 2026-06-17 · JSON

CVSS

6.5

v3.1 · NVD

CISA KEV

not known exploited

EPSS

1.1%

percentile 67%

Public exploits

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.

Exploit prediction (EPSS)

1.14% probability of exploitation in the next 30 days, higher than 67% of all scored CVEs.

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 only)

References

hackerone.com /reports/667408 · x_refsource_MISC, x_transferred

Sources

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

vulnwire keeps one entry per vulnerability: the CVE id wins, then GHSA; records that alias each other are merged. Machine-readable: JSON.