CVE-2025-6601 | Business Logic Errors in GitLab

GitLab has remediated an issue in GitLab EE affecting all versions from 18.4 before 18.4.3, and 18.5 before 18.5.1 that under certain conditions could have allowed authenticated users to gain unauthorized project access by exploiting the access request approval workflow.

Published: 2025-10-27 Last update: 2025-10-28 Assigner: [email protected] Source: [email protected]
NVD Status：Analyzed，CVE State: published
View at NVD, CVE.org, EUVD

CVE-2025-6601 is rated Low Risk (11.1/100): CVSS Low severity, with low exploitation likelihood (EPSS 0.01%). Low composite risk—no urgent action required; patch on your normal maintenance cycle and revisit priority if CVSS or EPSS increases.

Risk is dynamic; we continuously reassess and refresh what is shown on this page as upstream context changes.

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

EPSS lead: Daily EPSS estimates relative likelihood of exploitation; percentile ranks this CVE among scored vulnerabilities (higher = more severe relative rank).

# Date Old EPSS score New EPSS score Delta (New - Old)
1 2025-10-27 — 0.01% —

Full EPSS history (1 record total)

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

CVSS metrics for this CVE.

Base score Version Severity Vector Exploitability Impact Score source
2.7 3.1 LOW
CVSS:3.1/AV:N/AC:L/PR:H/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:H)
They need powerful rights—admin, root, or similar—before this pays off.
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.
 1.2 1.4 [email protected]
6.5 3.1 MEDIUM
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/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: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:N)
Doesn’t really leak secrets in a meaningful 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.
 2.8 3.6 [email protected]

Weakness enumeration for CVE-2025-6601

OS Trackers for CVE-2025-6601

vendor priority summary link
debian unimportant CVE-2025-6601 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-6601
ubuntu medium CVE-2025-6601 medium priority: Ubuntu including 1 source packages (gitlab), 6 status rows across 6 suites (jammy, noble, plucky, questing, upstream, xenial): DNE 4, ignored 1, not-affected 1. https://ubuntu.com/security/CVE-2025-6601

Affected software / configurations for CVE-2025-6601

Vendor Product Version Raw CPE
gitlab gitlab >= 18.4.0, < 18.4.3 cpe:2.3:a:gitlab:gitlab:*:*:*:*:enterprise:*:*:*
gitlab gitlab 18.5.0 cpe:2.3:a:gitlab:gitlab:18.5.0:*:*:*:enterprise:*:*:*

References for CVE-2025-6601

cvelogic Threat Intelligence