dbcve.org
GitLabApplication

CVE-2025-3279

MEDIUM · 6.5 CVSS v3.1 Published 2025-06-26
Fix available
A fix is available. Upgrade to 17.11.5 / 18.0.3 or later.
See remediation →
71/100
Remediation priority · Elevated
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
An issue has been discovered in GitLab CE/EE affecting all versions from 10.7 before 17.11.5, 18.0 before 18.0.3, and 18.1 before 18.1.1 that could have allowed authenticated attackers to create a DoS condition by sending crafted GraphQL requests.

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 confidence

A denial-of-service vulnerability in GitLab's GraphQL API allows authenticated attackers to crash or hang the service by sending specially crafted GraphQL requests, affecting versions 10.7 through 17.11.4, 18.0.0-18.0.2, and 18.1.0.

MitigationUpgrade GitLab to version 17.11.5, 18.0.3, 18.1.1 or later to patch the vulnerability. Until upgraded, monitor GraphQL endpoint access and consider rate limiting authenticated users.

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:>= 10.7.0, < 17.11.5>= 18.0.0, < 18.0.3= 18.1.0

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

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H

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. Identify installed GitLab version
    Run `sudo gitlab-rake gitlab:env:info` or check `/opt/gitlab/version` to obtain the exact version number. Alternatively, visit Admin Area > Settings > Metrics and profiling > Version on the web interface.
    Affected if The installed version falls within 10.7.0 to 17.11.4, 18.0.0 to 18.0.2, or equals 18.1.0 (before 17.11.5, 18.0.3, or 18.1.1).
  2. Confirm GraphQL API is accessible
    Verify the GraphQL endpoint is reachable at `https://<gitlab-host>/api/graphql` or `<gitlab-host>/-/graphql` and responds to requests. This is enabled by default in standard GitLab installations.
    Affected if The GraphQL endpoint is exposed and accepts requests from authenticated users.
  3. Verify user authentication is enabled for GraphQL
    Check that GitLab's authentication is required for GraphQL access. In Admin Area > Settings > General > Visibility and access controls, confirm that unauthenticated GraphQL access is not permitted.
    Affected if Authenticated users can access the GraphQL API, which is the default configuration.
  4. Inspect for service instability or crash indicators
    Review GitLab logs for signs of denial-of-service: run `sudo gitlab-ctl tail | grep -i graphql` and check `/var/log/gitlab/gitlab-rails/production.log` for repeated failures, timeouts, or memory exhaustion related to GraphQL queries.
    Affected if The service has experienced crashes, hangs, or GraphQL-related timeouts since the vulnerability disclosure, especially from authenticated user requests.

You are affected if your GitLab version is between 10.7.0 and 17.11.4, 18.0.0-18.0.2, or 18.1.0, and the GraphQL API is accessible to authenticated users.

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 17.11.5 / 18.0.3 or later
Fixed in 17.11.518.0.3
Interim mitigation

Upgrade GitLab to version 17.11.5, 18.0.3, 18.1.1 or later to patch the vulnerability. Until upgraded, monitor GraphQL endpoint access and consider rate limiting authenticated users.

Recommended fix High confidence

17.11.5 (or later 17.x), 18.0.3 (or later 18.0.x), or 18.1.1 (or later 18.1.x)

  1. Identify the currently installed GitLab version using `gitlab-rake gitlab:env:info` or the GitLab admin area
  2. Ensure you have a complete backup of your GitLab instance before upgrading
  3. Plan for appropriate downtime based on your instance size
  4. For GitLab installations using the official packages (Omnibus), upgrade to version 17.11.5 or later in the 17.x stable branch
  5. For GitLab 18.0.x installations, upgrade to version 18.0.3 or later
  6. For GitLab 18.1.0 installations, upgrade to version 18.1.1 or later
  7. After upgrade, verify GitLab is functioning correctly and test GraphQL functionality
  8. Review GitLab release notes for any additional required post-upgrade migrations
Caveat Major version upgrades (e.g., 17.x to 18.x) may require database migrations and can have compatibility implications; review GitLab upgrade docs for specific version jumps

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in GitLab Scoped from the published advisory
  • Consultation3.0 h
  • Implementation4.0 h
  • Testing3.0 h
  • Review / QA2.0 h
12.0 hours of engineering $2,130
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,408.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2025-3279 — 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-3279 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