Unauthorized experiment creation via membership check omission
Published Sep 1, 2023 · Updated Aug 14, 2026
Improper authorization in GitLab 16.2 through 16.2.4 and 16.3.0 allows remote authenticated users to create model experiments in public projects. The model-experiment API entrypoint validates only the access-token scope and fails to verify that the caller belongs to the target project. Any authenticated non-member with an API-scoped token can add experiment records and read experiment data when the feature is enabled for a public project.
Summary
What happened
Improper authorization in GitLab 16.2 through 16.2.4 and 16.3.0 allows remote authenticated users to create model experiments in public projects. The model-experiment API entrypoint validates only the access-token scope and fails to verify that the caller belongs to the target project. Any authenticated non-member with an API-scoped token can add experiment records and read experiment data when the feature is enabled for a public project.
The record
- CVE
- CVE-2023-4018
- Published
- Sep 1, 2023
- Updated
- Aug 14, 2026
- Vendor
- GitLab
- Product
- GitLab
- Classifications
- CWE-425, T1565.001
- Attack vector
- network
- Privileges
- authenticated
Timeline
How it unfolded
- Sep 1, 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=16.2 <16.2.5
- Affected versionversion=16.3 <16.3.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
- HackerOne report 2083440 reproductionproof of concept · unverified
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