CVE-2025-14592 [Low] | Security Vulnerability in Gitlab

GitLab has remediated an issue in GitLab CE/EE affecting all versions from 18.6 before 18.6.6, 18.7 before 18.7.4, and 18.8 before 18.8.4 that, under certain conditions could have allowed an authenticated user to perform unauthorized operations by submitting GraphQL mutations through the GLQL API endpoint.

#	Date	Old EPSS score	New EPSS score	Delta (New - Old)
1	2026-06-15	0.01%	0.25%	+0.24%
2	2026-02-11	—	0.01%	—

Date

Old EPSS score

New EPSS score

Delta (New - Old)

2026-06-15

0.01%

0.25%

+0.24%

2026-02-11

—

0.01%

—

Base score	Version	Severity	Vector	Exploitability	Impact	Score source
3.7	3.1	LOW	`CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:L/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: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:N) Doesn’t really leak secrets in a meaningful way. Integrity (I:L) Attackers could change some data, but it’s limited—not everything goes. Availability (A:N) Service keeps running; no real outage angle.	2.2	1.4	[email protected]
5.3	3.1	MEDIUM	`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/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:N) Doesn’t really leak secrets in a meaningful way. Integrity (I:L) Attackers could change some data, but it’s limited—not everything goes. Availability (A:N) Service keeps running; no real outage angle.	3.9	1.4	[email protected]

Base score

Version

Severity

Vector

Exploitability

Impact

Score source

3.7

3.1

LOW

CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:L/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: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:N): Doesn’t really leak secrets in a meaningful way.
Integrity (I:L): Attackers could change some data, but it’s limited—not everything goes.
Availability (A:N): Service keeps running; no real outage angle.

2.2

1.4

[email protected]

5.3

3.1

MEDIUM

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/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:N): Doesn’t really leak secrets in a meaningful way.
Integrity (I:L): Attackers could change some data, but it’s limited—not everything goes.
Availability (A:N): Service keeps running; no real outage angle.

3.9

1.4

[email protected]

OS Trackers for CVE-2025-14592

vendor	priority	summary	link
`debian`	unimportant	CVE-2025-14592 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-14592
`ubuntu`	medium	CVE-2025-14592 medium priority: Ubuntu including 2 source packages (gitlab, gitlab-agent), 9 status rows across 5 suites (jammy, noble, questing, upstream, xenial): DNE 4, needs-triage 4, ignored 1.	https://ubuntu.com/security/CVE-2025-14592

Affected software / configurations for CVE-2025-14592

Vendor	Product	Version	Raw CPE
gitlab	gitlab	>= 18.6.0, < 18.6.6	cpe:2.3:a:gitlab:gitlab:::::community:::*
gitlab	gitlab	>= 18.6.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-14592

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/583961	Broken Link Issue Tracking
https://hackerone.com/reports/3451435	Permissions Required

URL

CVE-2025-14592 | Missing Authorization in GitLab

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

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

Weakness enumeration for CVE-2025-14592

OS Trackers for CVE-2025-14592

Affected software / configurations for CVE-2025-14592

References for CVE-2025-14592