CVE-2025-5819 | Incorrect Permission Assignment for Critical Resource in GitLab

An issue has been discovered in GitLab CE/EE affecting all versions from 15.7 before 18.0.6, 18.1 before 18.1.4, and 18.2 before 18.2.2 that could have allowed authenticated users with developer access to obtain ID tokens for protected branches under certain circumstances.

Published: 2025-08-13 Last update: 2025-08-29 Assigner: [email protected] Source: [email protected]

Conclusion & alert: CVE-2025-5819 is rated Low Risk (20.4/100): CVSS Medium severity, with low exploitation likelihood (EPSS 0.01%). Mandatory action: Monitor for updates and reassess as exploit intelligence or EPSS changes.

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-5819

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-08-14 0.01%

Full EPSS history (1 record total)

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

CVSS metrics for this CVE.

Base score Version Severity Vector Exploitability Impact Score source
5.0 3.1 MEDIUM
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/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: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:C)
Breaking this can reach past the original component and bite other resources—bigger blast radius.
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.1 1.4 [email protected]

Weakness enumeration for CVE-2025-5819

OS Trackers for CVE-2025-5819

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

Affected software / configurations for CVE-2025-5819

Vendor Product Version Raw CPE
gitlab gitlab >= 15.7.0, < 17.11.6 cpe:2.3:a:gitlab:gitlab:*:*:*:*:community:*:*:*
gitlab gitlab >= 15.7.0, < 17.11.6 cpe:2.3:a:gitlab:gitlab:*:*:*:*:enterprise:*:*:*
gitlab gitlab >= 18.0.0, < 18.0.4 cpe:2.3:a:gitlab:gitlab:*:*:*:*:community:*:*:*
gitlab gitlab >= 18.0.0, < 18.0.4 cpe:2.3:a:gitlab:gitlab:*:*:*:*:enterprise:*:*:*
gitlab gitlab >= 18.1.0, < 18.1.2 cpe:2.3:a:gitlab:gitlab:*:*:*:*:community:*:*:*
gitlab gitlab >= 18.1.0, < 18.1.2 cpe:2.3:a:gitlab:gitlab:*:*:*:*:enterprise:*:*:*

References for CVE-2025-5819

cvelogic Threat Intelligence