An issue was discovered in GitLab Community Edition 11.x before 11.1.8, 11.2.x before 11.2.5, and 11.3.x before 11.3.2.

published 2018-12-04 7y ago modified 2026-06-17 4mo ago also EUVD-2018-9715

cvss: 5.3; version 3.0, 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 issue was discovered in GitLab Community Edition 11.x before 11.1.8, 11.2.x before 11.2.5, and 11.3.x before 11.3.2. There is Information Exposure via the GFM markdown API.

Patch / fix

fixed in 1

gitlab gitlab 11.1.8, 11.2.5, 11.3.2

Is CVE-2018-17975 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

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

Exploits and checks

gitlab.com https://gitlab.com/gitlab-org/gitlab-ce/issues/50744 referenced PoC, tagged "exploit" by a source, unverified

CVSS scores

assigned by	version	score	vector
NVD	3.0	5.3	CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N
NVD	2.0	5.0	AV:N/AC:L/Au:N/C:P/I:N/A:N

Classification

Weakness

CWE-200 Exposure of Sensitive Information to an Unauthorized Actor

Technology feeds

GitLab rss critical rss

References

gitlab.com /gitlab-org/gitlab-ce/issues/50744
exploit, issue-tracking, vendor-advisory
about.gitlab.com /2018/10/05/critical-security-release-11-3-4/
vendor-advisory

Sources

CVE List CVE-2018-17975
NVD CVE-2018-17975

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.