CVE-2024-8641 [Medium] | Security Vulnerability in Gitlab

An issue has been discovered in GitLab CE/EE affecting all versions starting from 13.7 prior to 17.1.7, from 17.2 prior to 17.2.5, and from 17.3 prior to 17.3.2. It may have been possible for an attacker with a victim's CI_JOB_TOKEN to obtain a GitLab session token belonging to the victim.

#	Date	Old EPSS score	New EPSS score	Delta (New - Old)
1	2026-06-15	0.06%	0.46%	+0.40%
2	2026-02-01	0.04%	0.06%	+0.02%
3	2025-11-21	—	0.04%	—

Date

Old EPSS score

New EPSS score

Delta (New - Old)

2026-06-15

0.06%

0.46%

+0.40%

2026-02-01

0.04%

0.06%

+0.02%

2025-11-21

—

0.04%

—

Base score	Version	Severity	Vector	Exploitability	Impact	Score source
6.7	3.1	MEDIUM	`CVSS:3.1/AV:N/AC:H/PR:L/UI:R/S:U/C:H/I:H/A:L` 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:R) A real person has to do something—click, install, enable—otherwise it doesn’t land. 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:L) Might cause slowdowns, glitches, or partial disruption—not a full brick.	1.2	5.5	[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

6.7

3.1

MEDIUM

CVSS:3.1/AV:N/AC:H/PR:L/UI:R/S:U/C:H/I:H/A:L 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:R): A real person has to do something—click, install, enable—otherwise it doesn’t land.
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:L): Might cause slowdowns, glitches, or partial disruption—not a full brick.

1.2

5.5

[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-2024-8641

vendor	priority	summary	link
`debian`	not yet assigned	CVE-2024-8641 not yet assigned priority: Debian including 1 source packages (gitlab), 1 status rows across 1 suites (sid): resolved 1.	https://security-tracker.debian.org/tracker/CVE-2024-8641
`ubuntu`	medium	CVE-2024-8641 medium priority: Ubuntu including 1 source packages (gitlab), 5 status rows across 5 suites (focal, jammy, noble, upstream, xenial): DNE 3, ignored 1, released 1.	https://ubuntu.com/security/CVE-2024-8641

Affected software / configurations for CVE-2024-8641

Vendor	Product	Version	Raw CPE
gitlab	gitlab	>= 13.7.0, < 17.1.7	cpe:2.3:a:gitlab:gitlab:::::community:::*
gitlab	gitlab	>= 13.7.0, < 17.1.7	cpe:2.3:a:gitlab:gitlab:::::enterprise:::*
gitlab	gitlab	>= 17.2.0, < 17.2.5	cpe:2.3:a:gitlab:gitlab:::::community:::*
gitlab	gitlab	>= 17.2.0, < 17.2.5	cpe:2.3:a:gitlab:gitlab:::::enterprise:::*
gitlab	gitlab	>= 17.3.0, < 17.3.2	cpe:2.3:a:gitlab:gitlab:::::community:::*
gitlab	gitlab	>= 17.3.0, < 17.3.2	cpe:2.3:a:gitlab:gitlab:::::enterprise:::*

References for CVE-2024-8641

URL	Tags
https://gitlab.com/gitlab-org/gitlab/-/issues/471954	Broken Link
https://hackerone.com/reports/2595495	Permissions Required
https://about.gitlab.com/releases/2024/09/11/patch-release-gitlab-17-3-2-released/

URL

CVE-2024-8641 | Privilege Context Switching Error in GitLab

Exploit prediction scoring system (EPSS) score for CVE-2024-8641

Common vulnerability scoring system (CVSS) metrics for CVE-2024-8641

Weakness enumeration for CVE-2024-8641

OS Trackers for CVE-2024-8641

Affected software / configurations for CVE-2024-8641

References for CVE-2024-8641