CVE-2025-2242 [High] | Security Vulnerability in Gitlab

An improper access control vulnerability in GitLab CE/EE affecting all versions from 17.4 prior to 17.8.6, 17.9 prior to 17.9.3, and 17.10 prior to 17.10.1 allows a user who was an instance admin before but has since been downgraded to a regular user to continue to maintain elevated privileges to groups and projects.

#	Date	Old EPSS score	New EPSS score	Delta (New - Old)
1	2026-05-05	0.05%	0.03%	-0.03%
2	2026-05-04	0.01%	0.05%	+0.04%
3	2025-03-28	—	0.01%	—

Date

Old EPSS score

New EPSS score

Delta (New - Old)

2026-05-05

0.05%

0.03%

-0.03%

2026-05-04

0.01%

0.05%

+0.04%

2025-03-28

—

0.01%

—

Base score	Version	Severity	Vector	Exploitability	Impact	Score source
7.5	3.1	HIGH	`CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:U/C:H/I:H/A:H` 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:H) Even with access, the exploit needs extra luck, timing, or a fussy environment to actually work. 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:H) Serious risk that confidential data gets exposed in a big way. Integrity (I:H) They could widely tamper with or forge data—trust in the data is badly hurt. Availability (A:H) Could take the service down hard or make it unusable for people who depend on it.	1.6	5.9	[email protected]
8.8	3.1	HIGH	`CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H` 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:H) Serious risk that confidential data gets exposed in a big way. Integrity (I:H) They could widely tamper with or forge data—trust in the data is badly hurt. Availability (A:H) Could take the service down hard or make it unusable for people who depend on it.	2.8	5.9	[email protected]

Base score

Version

Severity

Vector

Exploitability

Impact

Score source

7.5

3.1

HIGH

CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:U/C:H/I:H/A:H 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:H): Even with access, the exploit needs extra luck, timing, or a fussy environment to actually work.
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:H): Serious risk that confidential data gets exposed in a big way.
Integrity (I:H): They could widely tamper with or forge data—trust in the data is badly hurt.
Availability (A:H): Could take the service down hard or make it unusable for people who depend on it.

1.6

5.9

[email protected]

8.8

3.1

HIGH

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H 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:H): Serious risk that confidential data gets exposed in a big way.
Integrity (I:H): They could widely tamper with or forge data—trust in the data is badly hurt.
Availability (A:H): Could take the service down hard or make it unusable for people who depend on it.

2.8

5.9

[email protected]

OS Trackers for CVE-2025-2242

vendor	priority	summary	link
`debian`	not yet assigned	CVE-2025-2242 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-2242
`ubuntu`	medium	CVE-2025-2242 medium priority: Ubuntu including 1 source packages (gitlab), 6 status rows across 6 suites (focal, jammy, noble, oracular, upstream, xenial): DNE 4, ignored 1, needs-triage 1.	https://ubuntu.com/security/CVE-2025-2242

Affected software / configurations for CVE-2025-2242

Vendor	Product	Version	Raw CPE
gitlab	gitlab	>= 17.4.0, < 17.8.6	cpe:2.3:a:gitlab:gitlab:::::community:::*
gitlab	gitlab	>= 17.4.0, < 17.8.6	cpe:2.3:a:gitlab:gitlab:::::enterprise:::*
gitlab	gitlab	>= 17.9.0, < 17.9.3	cpe:2.3:a:gitlab:gitlab:::::community:::*
gitlab	gitlab	>= 17.9.0, < 17.9.3	cpe:2.3:a:gitlab:gitlab:::::enterprise:::*
gitlab	gitlab	17.10.0	cpe:2.3:a:gitlab:gitlab:17.10.0::::community:::
gitlab	gitlab	17.10.0	cpe:2.3:a:gitlab:gitlab:17.10.0::::enterprise:::

References for CVE-2025-2242

URL	Tags
https://gitlab.com/gitlab-org/gitlab/-/issues/516271	Broken Link

URL

CVE-2025-2242 | Incorrect Authorization in GitLab

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

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

Weakness enumeration for CVE-2025-2242

OS Trackers for CVE-2025-2242

Affected software / configurations for CVE-2025-2242

References for CVE-2025-2242