dbcve.org
GitLabApplication

CVE-2025-11340

HIGH · 7.7 CVSS v3.1 Published 2025-10-09
Fix available
A fix is available. Upgrade to 18.3.4 / 18.4.2 or later.
See remediation →
83/100
Remediation priority · High
Remotely reachable Zero-click

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 · unedited
GitLab has remediated an issue in GitLab EE affecting all versions from 18.3 to 18.3.4, 18.4 to 18.4.2 that, under certain conditions, could have allowed authenticated users with read-only API tokens to perform unauthorized write operations on vulnerability records by exploiting incorrectly scoped GraphQL mutations.

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 · moderate confidence

In affected GitLab EE versions (18.3.x and 18.4.x), an authorization bypass existed where authenticated users holding read-only API tokens could perform write operations on vulnerability records by exploiting incorrectly scoped GraphQL mutations. The GraphQL API failed to properly enforce token scope restrictions, allowing mutation operations despite tokens being granted read-only permissions.

MitigationUpgrade GitLab EE to version 18.3.5, 18.4.3, or later to obtain the vendor patch. Review existing API tokens and monitor for any unauthorized vulnerability record modifications that may have occurred while vulnerable.

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
Affected:>= 18.3.0, < 18.3.4>= 18.4.0, < 18.4.2

CVSS 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
Changed
Confidentiality
None
Integrity
High
Availability
None

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:N/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 checks

Work through these to decide whether this CVE applies to you.

  1. Determine installed GitLab EE version
    Run 'sudo gitlab-rake gitlab:env:info' or check the GitLab admin area under /admin/application_settings or look at /opt/gitlab/version-manifest.txt
    Affected if Version is 18.3.0-18.3.3 or 18.4.0-18.4.1 (vulnerable ranges)
  2. Verify GraphQL API endpoint accessibility
    Confirm the GraphQL endpoint is accessible at /api/graphql - check if the instance has GraphQL enabled and exposed
    Affected if GraphQL API is accessible without additional restrictions (prerequisite for the attack)
  3. Review existing API tokens for read-only scopes
    List API tokens in GitLab admin area under /admin/api_tokens or use the API: GET /users/:user_id/personal_access_tokens, looking for tokens with 'read_api' or 'read_only' scope
    Affected if Read-only API tokens exist in the system (potential attack vector)
  4. Audit vulnerability record modifications
    Query the vulnerabilities API endpoint or review the vulnerabilities page in the UI for unexpected changes to vulnerability status, severity, or metadata
    Affected if Unauthorized or unexpected modifications to vulnerability records are found

You are affected if your GitLab EE version falls within 18.3.0-18.3.3 or 18.4.0-18.4.1 AND read-only API tokens can access the GraphQL API, regardless of whether unauthorized changes are detected in logs.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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 · scoped
Upgrade available Upgrade to 18.3.4 / 18.4.2 or later
Fixed in 18.3.418.4.2
Interim mitigation

Upgrade GitLab EE to version 18.3.5, 18.4.3, or later to obtain the vendor patch. Review existing API tokens and monitor for any unauthorized vulnerability record modifications that may have occurred while vulnerable.

Recommended fix High confidence

18.3.4 or 18.4.2 (preferably latest 18.4.x)

  1. 1. Back up your current GitLab instance and database before upgrading.
  2. 2. Identify your current GitLab version using `sudo gitlab-rake gitlab:env:info` or the GitLab admin panel.
  3. 3. If running version 18.3.0 through 18.3.3, upgrade to version 18.3.4 or later.
  4. 4. If running version 18.4.0 or 18.4.1, upgrade to version 18.4.2 or later.
  5. 5. For the smoothest path, upgrade to the latest stable 18.4.x release (currently 18.4.2 or higher).
  6. 6. After upgrade, verify the instance is operational and test that read-only API tokens no longer have write access to vulnerability records.
Caveat Review GitLab 18.3 and 18.4 release notes for any breaking changes between your current version and target version; minor version upgrades typically have low risk but always test in staging first

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 / QA2.0 h
14.0 hours of engineering $2,380
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,808.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2025-11340 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2025-11340 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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