An issue was discovered in GitLab Community and Enterprise Edition 10.8 through 12.2.1.

published 2019-09-16 7y ago modified 2026-06-17 4mo ago also EUVD-2019-6657

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

An issue was discovered in GitLab Community and Enterprise Edition 10.8 through 12.2.1. An internal endpoint unintentionally allowed group maintainers to view and edit group runner settings.

Patch / fix

fixed in 1

gitlab gitlab 12.0.8, 12.1.8, 12.2.3

Is CVE-2019-15721 in your stack? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.

Check with Fencer

Exploit prediction

0.76% chance of exploitation in the next 30 days, higher than 55% of all scored CVEs (FIRST EPSS, 2026-11-09).

CVSS scores

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

Classification

Weakness

CWE-732 Incorrect Permission Assignment for Critical Resource

Technology feeds

GitLab rss critical rss

References

about.gitlab.com /2019/08/29/security-release-gitlab-12-dot-2-dot-3-released/
release-notes, vendor-advisory
gitlab.com /gitlab-org/gitlab-ce/issues/61981
broken-link

Sources

CVE List CVE-2019-15721
NVD CVE-2019-15721

Fencer Intel 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.