Unauthorized commit creation via unchecked GLQL mutation
Published Feb 11, 2026 · Updated Feb 11, 2026
Missing authorization in GitLab CE/EE allows remote authenticated users to create unauthorized commits through the GLQL API endpoint. The endpoint accepts a commitCreate GraphQL mutation under a personal access token limited to read_api without enforcing the token's write restrictions. Exploitation requires possession of another user's read_api token and permits changes to a private project repository without broader API write scope.
Summary
What happened
Missing authorization in GitLab CE/EE allows remote authenticated users to create unauthorized commits through the GLQL API endpoint. The endpoint accepts a commitCreate GraphQL mutation under a personal access token limited to read_api without enforcing the token's write restrictions. Exploitation requires possession of another user's read_api token and permits changes to a private project repository without broader API write scope.
The record
- CVE
- CVE-2025-14592
- Published
- Feb 11, 2026
- Updated
- Feb 11, 2026
- Vendor
- GitLab
- Product
- GitLab
- Classifications
- CWE-862, T1078
- Attack vector
- network
- Privileges
- authenticated
Timeline
How it unfolded
- Feb 11, 2026CVE publishedPublication date reported by the CVE source.
- Feb 11, 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=18.6 <18.6.6
- Affected versionversion=18.7 <18.7.4
- Affected versionversion=18.8 <18.8.4
What conditions does exploitation require?
What is affected?
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.
Public exploit references
- GitLab issue reproduction for read_api permission bypassproof 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