Group fork restriction bypass via missing authorization
Published Apr 22, 2026 · Updated Apr 22, 2026
Incorrect authorization in GitLab CE/EE allows remote authenticated users to bypass group fork prevention settings through its API. The project fork relationship API fails to enforce a parent group's fork-prevention policy when an owner creates the relationship. Project owner permissions are required, and exploitation creates a fork relationship that the group's policy is intended to prohibit; no confidentiality or availability impact is reported.
Summary
What happened
Incorrect authorization in GitLab CE/EE allows remote authenticated users to bypass group fork prevention settings through its API. The project fork relationship API fails to enforce a parent group's fork-prevention policy when an owner creates the relationship. Project owner permissions are required, and exploitation creates a fork relationship that the group's policy is intended to prohibit; no confidentiality or availability impact is reported.
The record
- CVE
- CVE-2025-9957
- Published
- Apr 22, 2026
- Updated
- Apr 22, 2026
- Vendor
- GitLab
- Product
- GitLab
- Classifications
- CWE-863
- Attack vector
- network
- Privileges
- admin
Timeline
How it unfolded
- Apr 22, 2026CVE publishedPublication date reported by the CVE source.
- Apr 22, 2026Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=11.2 <18.9.6
- Affected versionversion=18.10 <18.10.4
- Affected versionversion=18.11 <18.11.1
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo