CVE-2025-9957

GitLab has remediated an issue in GitLab CE/EE affecting all versions from 11.2 before 18.9.6, 18.10 before 18.10.4, and 18.11 before 18.11.1 that under certain conditions could have allowed an authenticated user with project owner permissions to bypass group fork prevention settings due to improper authorization checks.

Published: 2026-04-22 Last update: 2026-04-23 Assigner: [email protected] Source: [email protected]
NVD Status：Analyzed，CVE State: —
View at NVD, CVE.org, EUVD

CVE-2025-9957 is rated Low Risk (19/100): CVSS Low severity, with low exploitation likelihood (EPSS 0.31%). 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-9957

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 2026-06-15 0.01% 0.31% +0.30%
2 2026-04-23 — 0.01% —

Full EPSS history (2 records total)

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

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]

Weakness enumeration for CVE-2025-9957

GitHub Security Advisory for CVE-2025-9957

GHSA-6gww-qgc8-r365 · Severity: low — GitLab has remediated an issue in GitLab CE/EE affecting all versions from 11.2 before 18.9.6, 18...

OS Trackers for CVE-2025-9957

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

Affected software / configurations for CVE-2025-9957

Vendor Product Version Raw CPE
gitlab gitlab >= 11.2.0, < 18.9.6 cpe:2.3:a:gitlab:gitlab:*:*:*:*:community:*:*:*
gitlab gitlab >= 11.2.0, < 18.9.6 cpe:2.3:a:gitlab:gitlab:*:*:*:*:enterprise:*:*:*
gitlab gitlab >= 18.10.0, < 18.10.4 cpe:2.3:a:gitlab:gitlab:*:*:*:*:community:*:*:*
gitlab gitlab >= 18.10.0, < 18.10.4 cpe:2.3:a:gitlab:gitlab:*:*:*:*:enterprise:*:*:*
gitlab gitlab 18.11.0 cpe:2.3:a:gitlab:gitlab:18.11.0:*:*:*:community:*:*:*
gitlab gitlab 18.11.0 cpe:2.3:a:gitlab:gitlab:18.11.0:*:*:*:enterprise:*:*:*

References for CVE-2025-9957

cvelogic Threat Intelligence