Authorization Bypass Through User-Controlled Key in GitLab

published 2025-06-12 16 mo ago modified 2026-09-08 2 mo ago also BIT-gitlab-2025-5195 , EUVD-2025-18172

cvss: 4.3; version 3.1, CNA
cisa kev: Not listed; not in CISA's catalog
epss: 0.3%; EPSS 0.3% chance of exploitation in 30 days, percentile 23%
public exploits: 0; none known

An issue has been discovered in GitLab CE/EE affecting all versions from 17.9 before 17.10.7, 17.11 before 17.11.3, and 18.0 before 18.0.1. It was possible for authenticated users to access arbitrary compliance frameworks, leading to unauthorized data disclosure.

Patch / fix

fixed in 2

bitnami gitlab 18.0.2
GitLab GitLab 17.10.8, 17.11.4, 18.0.2

CISA SSVC

Exploitation: none
Automatable: no
Technical impact: partial
Assessed: 16 mo ago (2025-06-12)

Exploit prediction

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

Exploits and checks

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

CVSS scores

assigned by	version	score	vector
CNA	3.1	4.3	CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:N/A:N
OSV	3.1	4.3	CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:N/A:N

Affected packages

ecosystem	package	affected	fixed in
bitnami	gitlab	>=17.9.0, <18.0.2	18.0.2

Affected products

GitLab GitLab

Classification

Weakness

CWE-639 Authorization Bypass Through User-Controlled Key

Technology feeds

GitLab rss critical rss

References

gitlab.com /gitlab-org/gitlab/-/issues/534960
issue-tracking, permissions-required, exploit, evidence
nvd.nist.gov /vuln/detail/CVE-2025-5195
web

Sources

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.

CPEs and fixed versions use Anchore's correction of NVD's data: Added CPE configurations because not yet analyzed by NVD.

Summary