GitLabApplication
CVE-2026-1322
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedGitLab has remediated an issue in GitLab CE/EE affecting all versions from 16.0 before 18.9.7, 18.10 before 18.10.6, and 18.11 before 18.11.3 that could have allowed an authenticated user with a read_api scoped OAuth application to create issues and add comments to issues in private projects due to improper authorization.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · high confidenceGitLab had an improper authorization vulnerability where OAuth applications with only read_api scope could perform write operations (create issues, add comments) on private projects. The authorization check was not properly enforcing the read-only nature of the read_api scope.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.
NVD · CPE data
GitLabApplication
>= 16.0.0, < 18.9.7>= 18.10.0, < 18.10.6>= 18.11.0, < 18.11.3CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Network
- Complexity
- Low
- Privileges
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:N
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Check installed GitLab versionRun `sudo gitlab-rake gitlab:env:info` or check the /opt/gitlab/version file. Alternatively, visit Admin Area > Dashboard > Version in the web UI.Affected if The version falls within 16.0.0 to 18.9.6, 18.10.0 to 18.10.5, or 18.11.0 to 18.11.2 (i.e., any version >= 16.0.0 and < 18.9.7, >= 18.10.0 and < 18.10.6, or >= 18.11.0 and < 18.11.3)
-
Identify OAuth applications with read_api scopeIn Admin Area > Applications > OAuth Applications, review each application. Look for applications where the Scopes field includes read_api but no write_ scope.Affected if Any OAuth application exists with read_api scope granted (and no write scope) to access private projects
-
Audit issue creation activity from OAuth tokensQuery the database: `sudo gitlab-rails dbconsole` then `SELECT id, author_id, project_id, title, created_at FROM issues WHERE created_at > '2024-01-01' ORDER BY created_at DESC;` Cross-reference the author_id against OAuth token users in the oauth_access_tokens table.Affected if Issues were created by users authenticated via OAuth tokens that only have read_api scope
-
Audit note (comment) creation from OAuth tokensQuery: `SELECT id, author_id, project_id, noteable_type, created_at FROM notes WHERE noteable_type IN ('Issue', 'MergeRequest') AND created_at > '2024-01-01' ORDER BY created_at DESC;` Check if authors used OAuth tokens with only read_api scope.Affected if Comments were added to issues or merge requests by users authenticated via OAuth tokens that only have read_api scope
You are affected if your GitLab version is within the vulnerable range AND you have OAuth applications with read_api scope granting access to private projects, especially if unauthorized issue creation or commenting activity is present in the audit logs.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
dbcve · scoped18.9.718.10.618.11.3
Upgrade GitLab to version 18.9.7, 18.10.6, 18.11.3 or later. Audit OAuth applications with read_api scope to detect any unauthorized issue creation or commenting activity.
GitLab 18.11.3 or later (recommended: latest 18.11.x stable)
- 1. Back up your GitLab instance database and repositories before upgrading.
- 2. Review the GitLab upgrade documentation for your installation method (Omnibus, source, or Helm chart).
- 3. Stop GitLab services to ensure data integrity during the upgrade.
- 4. Update your GitLab package or source to version 18.11.3 or later (recommended: latest 18.11.x stable release).
- 5. Reconfigure GitLab: sudo gitlab-ctl reconfigure (for Omnibus installations).
- 6. Verify the upgrade completed successfully by checking the GitLab version in the Admin Area > Settings > General.
- 7. Confirm OAuth applications with read_api scope now correctly enforce authorization restrictions.
Generated from the published advisory — verify against the referenced sources before acting.
Fix this in GitLab
Scoped from the published advisory
- Consultation3.0 h
- Implementation6.0 h
- Testing3.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,984.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-1322 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2026-1322 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data