Unauthorized fork linkage via missing role enforcement
Published Sep 29, 2023 · Updated Aug 14, 2026
Incorrect authorization in affected GitLab versions allows remote authenticated users to create unauthorized fork relationships. The create-fork-relationship API accepts a Maintainer's authenticated POST request without enforcing its Owner-or-administrator authorization requirement. Maintainer access to the downstream project and access to an upstream project are sufficient to alter the fork topology, including by linking to a public project.
Summary
What happened
Incorrect authorization in affected GitLab versions allows remote authenticated users to create unauthorized fork relationships. The create-fork-relationship API accepts a Maintainer's authenticated POST request without enforcing its Owner-or-administrator authorization requirement. Maintainer access to the downstream project and access to an upstream project are sufficient to alter the fork topology, including by linking to a public project.
The record
- CVE
- CVE-2023-3920
- Published
- Sep 29, 2023
- Updated
- Aug 14, 2026
- Vendor
- GitLab
- Product
- GitLab
- Classifications
- CWE-863
- Attack vector
- network
- Privileges
- authenticated
Timeline
How it unfolded
- Sep 29, 2023CVE publishedPublication date reported by the CVE source.
- Aug 14, 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 <16.2.8
- Affected versionversion=16.3 <16.3.5
- Affected versionversion=16.4 <16.4.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
- Authenticated fork-relationship API proof of conceptproof of concept · demonstrated
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