CVE-2025-6171 [Medium] | Security Vulnerability in Gitlab

GitLab has remediated an issue in GitLab CE/EE affecting all versions from 13.2 before 18.3.6, 18.4 before 18.4.4, and 18.5 before 18.5.2 that could have allowed an authenticated attacker with reporter access to view branch names and pipeline details by accessing the packages API endpoint even when repository access was disabled.

#	Date	Old EPSS score	New EPSS score	Delta (New - Old)
1	2025-11-15	—	0.01%	—

Date

Old EPSS score

New EPSS score

Delta (New - Old)

2025-11-15

—

0.01%

—

Base score	Version	Severity	Vector	Exploitability	Impact	Score source
5.3	3.1	MEDIUM	`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N` Click to expand Attack vector (AV:N) Could be attacked over the internet or any normal routed network—not just someone sitting at the machine. Attack complexity (AC:L) Once they can reach the bug, pulling it off is straightforward—no weird race conditions or rare setup. Privileges required (PR:N) No account or special rights needed—anonymous or random user is enough. User interaction (UI:N) Nobody has to click “OK” or open a trap file; it can work without a victim helping. Scope (S:U) Damage stays in the same “trust bubble” as the broken component—no big spill into unrelated systems. Confidentiality (C:L) Some sensitive info could get out, but not a total data dump. Integrity (I:N) Data isn’t meaningfully altered or forged. Availability (A:N) Service keeps running; no real outage angle.	3.9	1.4	[email protected]
4.3	3.1	MEDIUM	`CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:N/A:N` Click to expand Attack vector (AV:N) Could be attacked over the internet or any normal routed network—not just someone sitting at the machine. Attack complexity (AC:L) Once they can reach the bug, pulling it off is straightforward—no weird race conditions or rare setup. Privileges required (PR:L) A normal user session is enough; they don’t have to be admin. User interaction (UI:N) Nobody has to click “OK” or open a trap file; it can work without a victim helping. Scope (S:U) Damage stays in the same “trust bubble” as the broken component—no big spill into unrelated systems. Confidentiality (C:L) Some sensitive info could get out, but not a total data dump. Integrity (I:N) Data isn’t meaningfully altered or forged. Availability (A:N) Service keeps running; no real outage angle.	2.8	1.4	[email protected]

Base score

Version

Severity

Vector

Exploitability

Impact

Score source

5.3

3.1

MEDIUM

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N Click to expand

Attack vector (AV:N): Could be attacked over the internet or any normal routed network—not just someone sitting at the machine.
Attack complexity (AC:L): Once they can reach the bug, pulling it off is straightforward—no weird race conditions or rare setup.
Privileges required (PR:N): No account or special rights needed—anonymous or random user is enough.
User interaction (UI:N): Nobody has to click “OK” or open a trap file; it can work without a victim helping.
Scope (S:U): Damage stays in the same “trust bubble” as the broken component—no big spill into unrelated systems.
Confidentiality (C:L): Some sensitive info could get out, but not a total data dump.
Integrity (I:N): Data isn’t meaningfully altered or forged.
Availability (A:N): Service keeps running; no real outage angle.

3.9

1.4

[email protected]

4.3

3.1

MEDIUM

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:N/A:N Click to expand

Attack vector (AV:N): Could be attacked over the internet or any normal routed network—not just someone sitting at the machine.
Attack complexity (AC:L): Once they can reach the bug, pulling it off is straightforward—no weird race conditions or rare setup.
Privileges required (PR:L): A normal user session is enough; they don’t have to be admin.
User interaction (UI:N): Nobody has to click “OK” or open a trap file; it can work without a victim helping.
Scope (S:U): Damage stays in the same “trust bubble” as the broken component—no big spill into unrelated systems.
Confidentiality (C:L): Some sensitive info could get out, but not a total data dump.
Integrity (I:N): Data isn’t meaningfully altered or forged.
Availability (A:N): Service keeps running; no real outage angle.

2.8

1.4

[email protected]

OS Trackers for CVE-2025-6171

vendor	priority	summary	link
`debian`	not yet assigned	CVE-2025-6171 not yet assigned priority: Debian including 1 source packages (gitlab), 1 status rows across 1 suites (sid): open 1.	https://security-tracker.debian.org/tracker/CVE-2025-6171
`ubuntu`	medium	CVE-2025-6171 medium priority: Ubuntu including 1 source packages (gitlab), 6 status rows across 6 suites (jammy, noble, plucky, questing, upstream, xenial): DNE 4, ignored 1, needs-triage 1.	https://ubuntu.com/security/CVE-2025-6171

Affected software / configurations for CVE-2025-6171

Vendor	Product	Version	Raw CPE
gitlab	gitlab	>= 13.2.0, < 18.3.6	cpe:2.3:a:gitlab:gitlab:::::community:::*
gitlab	gitlab	>= 13.2.0, < 18.3.6	cpe:2.3:a:gitlab:gitlab:::::enterprise:::*
gitlab	gitlab	>= 18.4.0, < 18.4.4	cpe:2.3:a:gitlab:gitlab:::::community:::*
gitlab	gitlab	>= 18.4.0, < 18.4.4	cpe:2.3:a:gitlab:gitlab:::::enterprise:::*
gitlab	gitlab	>= 18.5.0, < 18.5.2	cpe:2.3:a:gitlab:gitlab:::::community:::*
gitlab	gitlab	>= 18.5.0, < 18.5.2	cpe:2.3:a:gitlab:gitlab:::::enterprise:::*

References for CVE-2025-6171

URL	Tags
https://about.gitlab.com/releases/2025/11/12/patch-release-gitlab-18-5-2-released/	Release Notes Vendor Advisory
https://gitlab.com/gitlab-org/gitlab/-/issues/549730	Broken Link
https://hackerone.com/reports/3183740	Permissions Required

URL

CVE-2025-6171 | Missing Authorization in GitLab

Exploit prediction scoring system (EPSS) score for CVE-2025-6171

Common vulnerability scoring system (CVSS) metrics for CVE-2025-6171

Weakness enumeration for CVE-2025-6171

OS Trackers for CVE-2025-6171

Affected software / configurations for CVE-2025-6171

References for CVE-2025-6171