GitLabApplication
CVE-2026-4922
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 17.0 before 18.9.6, 18.10 before 18.10.4, and 18.11 before 18.11.1 that could have allowed an unauthenticated user to execute GraphQL mutations on behalf of authenticated users due to insufficient CSRF protection.
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 confidenceAn unauthenticated attacker could exploit insufficient CSRF protection in GitLab's GraphQL API to execute mutations on behalf of authenticated users, allowing unauthorized actions within GitLab by tricking authenticated users into triggering malicious requests.
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
>= 17.0.0, < 18.9.6>= 18.10.0, < 18.10.4= 18.11.0CVSS 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
- None
- User interaction
- Required
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/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.
-
Determine installed GitLab versionLog into the GitLab Admin area and navigate to Admin Area > Overview > System Info, or run `gitlab-rake gitlab:env:info` from the server console to retrieve the exact version number.Affected if The version falls within any of these ranges: >= 17.0.0 and < 18.9.6; >= 18.10.0 and < 18.10.4; or exactly 18.11.0
-
Verify GraphQL endpoint is accessibleAttempt to access the GraphQL endpoint at `/api/graphql` or `/-/graphql` on your GitLab instance using a web browser or curl command.Affected if The GraphQL endpoint returns a response (this is the vulnerable component); if it returns 404, the endpoint is not in use and the instance may not be at risk.
-
Confirm instance has active authenticated usersCheck the Admin Area > Users page to see if there are authenticated users, or query the database for user accounts with active status.Affected if The instance has authenticated users - the CSRF exploit targets authenticated users, so an instance with only anonymous or no users is less likely to be impacted.
You are affected if your GitLab version falls within the vulnerable ranges AND the GraphQL endpoint is accessible to your authenticated users.
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.618.10.4
Upgrade GitLab to versions 18.9.6, 18.10.4, 18.11.1 or later to receive the CSRF protection fix for the GraphQL endpoint.
18.11.1 (or 18.10.4 for 18.10.x branch, or 18.9.6 for 18.x branch)
- Identify your current GitLab version using the GitLab Rails console (gitlab-rails console) or the Admin Area > Overview > Dashboard
- Backup your GitLab instance database and repositories before upgrading
- Follow GitLab's official upgrade documentation for your installation method (Omnibus, source, or Helm chart)
- Upgrade to version 18.11.1 (or 18.10.4 if staying on 18.10.x, or 18.9.6 if staying on 18.x)
- Verify the upgrade was successful by checking the GitLab version in Admin Area > Overview > Dashboard
- Test GraphQL endpoint functionality to confirm normal operation
Generated from the published advisory — verify against the referenced sources before acting.
Fix this in GitLab
Scoped from the published advisory
- Consultation2.0 h
- Implementation4.0 h
- Testing6.0 h
- Review / QA3.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $4,096.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-4922 — 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-4922 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