Authenticated private-project writes via read-only OAuth scope
Published May 14, 2026 · Updated May 14, 2026
Improper authorization in GitLab CE/EE allows remote authenticated users to create issues and comments in private projects. Issue and comment creation endpoints accept state-changing API requests made with OAuth tokens limited to the read_api scope. A valid user context and a read_api-scoped OAuth application are required; successful requests alter private-project issue content without interrupting service.
Summary
What happened
Improper authorization in GitLab CE/EE allows remote authenticated users to create issues and comments in private projects. Issue and comment creation endpoints accept state-changing API requests made with OAuth tokens limited to the read_api scope. A valid user context and a read_api-scoped OAuth application are required; successful requests alter private-project issue content without interrupting service.
The record
- CVE
- CVE-2026-1322
- Published
- May 14, 2026
- Updated
- May 14, 2026
- Vendor
- GitLab
- Product
- GitLab
- Classifications
- CWE-840, T1190
- Attack vector
- network
- Privileges
- authenticated
Timeline
How it unfolded
- May 14, 2026CVE publishedPublication date reported by the CVE source.
- May 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.0 <18.9.7
- Affected versionversion=18.10 <18.10.6
- Affected versionversion=18.11 <18.11.3
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.
Public exploit references
- HackerOne disclosure reportproof 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