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

GitLab has remediated an issue in GitLab CE/EE affecting all versions from 18.2 before 18.6.6, 18.7 before 18.7.4, and 18.8 before 18.8.4 that could have allowed an unauthenticated user to steal tokens and access private repositories by abusing incomplete validation in the Web IDE.

#	Date	Old EPSS score	New EPSS score	Delta (New - Old)
1	2026-02-11	—	0.01%	—

Date

Old EPSS score

New EPSS score

Delta (New - Old)

2026-02-11

—

0.01%

—

Base score	Version	Severity	Vector	Exploitability	Impact	Score source
8.0	3.1	HIGH	`CVSS:3.1/AV:N/AC:H/PR:N/UI:R/S:C/C:H/I:H/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:H) Even with access, the exploit needs extra luck, timing, or a fussy environment to actually work. Privileges required (PR:N) No account or special rights needed—anonymous or random user is enough. User interaction (UI:R) A real person has to do something—click, install, enable—otherwise it doesn’t land. Scope (S:C) Breaking this can reach past the original component and bite other resources—bigger blast radius. 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:N) Service keeps running; no real outage angle.	1.6	5.8	[email protected]
9.1	3.1	CRITICAL	`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/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: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:N) Service keeps running; no real outage angle.	3.9	5.2	[email protected]

Base score

Version

Severity

Vector

Exploitability

Impact

Score source

8.0

3.1

HIGH

CVSS:3.1/AV:N/AC:H/PR:N/UI:R/S:C/C:H/I:H/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:H): Even with access, the exploit needs extra luck, timing, or a fussy environment to actually work.
Privileges required (PR:N): No account or special rights needed—anonymous or random user is enough.
User interaction (UI:R): A real person has to do something—click, install, enable—otherwise it doesn’t land.
Scope (S:C): Breaking this can reach past the original component and bite other resources—bigger blast radius.
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:N): Service keeps running; no real outage angle.

1.6

5.8

[email protected]

9.1

3.1

CRITICAL

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/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: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:N): Service keeps running; no real outage angle.

3.9

5.2

[email protected]

OS Trackers for CVE-2025-7659

vendor	priority	summary	link
`debian`	unimportant	CVE-2025-7659 unimportant priority: Debian including 1 source packages (gitlab), 1 status rows across 1 suites (sid): resolved 1.	https://security-tracker.debian.org/tracker/CVE-2025-7659
`ubuntu`	high	CVE-2025-7659 high priority: Ubuntu including 2 source packages (gitlab, gitlab-agent), 9 status rows across 5 suites (jammy, noble, questing, upstream, xenial): DNE 4, needs-triage 2, not-affected 2, ignored 1.	https://ubuntu.com/security/CVE-2025-7659

Affected software / configurations for CVE-2025-7659

Vendor	Product	Version	Raw CPE
gitlab	gitlab	>= 18.2.0, < 18.6.6	cpe:2.3:a:gitlab:gitlab:::::community:::*
gitlab	gitlab	>= 18.2.0, < 18.6.6	cpe:2.3:a:gitlab:gitlab:::::enterprise:::*
gitlab	gitlab	>= 18.7.0, < 18.7.4	cpe:2.3:a:gitlab:gitlab:::::community:::*
gitlab	gitlab	>= 18.7.0, < 18.7.4	cpe:2.3:a:gitlab:gitlab:::::enterprise:::*
gitlab	gitlab	>= 18.8.0, < 18.8.4	cpe:2.3:a:gitlab:gitlab:::::community:::*
gitlab	gitlab	>= 18.8.0, < 18.8.4	cpe:2.3:a:gitlab:gitlab:::::enterprise:::*

References for CVE-2025-7659

URL	Tags
https://about.gitlab.com/releases/2026/02/10/patch-release-gitlab-18-8-4-released/	Release Notes Vendor Advisory
https://gitlab.com/gitlab-org/gitlab/-/issues/555440	Broken Link Issue Tracking
https://hackerone.com/reports/3234976	Permissions Required

URL

CVE-2025-7659 | Origin Validation Error in GitLab

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

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

Weakness enumeration for CVE-2025-7659

OS Trackers for CVE-2025-7659

Affected software / configurations for CVE-2025-7659

References for CVE-2025-7659