dbcve.org
GitLabApplication

CVE-2025-2614

MEDIUM · 6.5 CVSS v3.1 Published 2025-08-13
Fix available
A fix is available. Upgrade to 18.0.6 / 18.1.4 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 11.6 before 18.0.6, 18.1 before 18.1.4, and 18.2 before 18.2.2 that could have allowed an authenticated user to cause a denial of service condition by creating specially crafted content that consumes excessive server resources when processed.

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

An authenticated user can cause a denial of service condition in GitLab CE/EE by creating specially crafted content that consumes excessive server resources during processing. This affects all versions from 11.6 through the vulnerable releases (18.0.x before 18.0.6, 18.1.x before 18.1.4, and 18.2.x before 18.2.2).

MitigationUpgrade GitLab to version 18.0.6, 18.1.4, 18.2.2 or later to remediate this vulnerability.

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:>= 11.6.0, < 18.0.6>= 18.1.0, < 18.1.4>= 18.2.0, < 18.2.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
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. Check installed GitLab version
    Run `sudo gitlab-rake gitlab:version` or check the GitLab admin panel under Help > Version. Alternatively, check the package version with `dpkg -l | grep gitlab-ee` or `rpm -qa | grep gitlab` depending on your OS.
    Affected if The version is within 11.6.0 to 18.0.5, 18.1.0 to 18.1.3, or 18.2.0 to 18.2.1 (all versions from 11.6.0 up to but not including 18.0.6, 18.1.4, or 18.2.2).
  2. Confirm GitLab edition
    Verify whether you are running GitLab Community Edition (CE) or Enterprise Edition (EE) using `sudo gitlab-rake gitlab:env:info` or the admin panel. Both editions are affected.
    Affected if Running either GitLab CE or EE on a version listed in the affected version ranges.
  3. Identify if users have authenticated access
    Review your GitLab instance to determine whether any authenticated users exist. Check user count in Admin Area > Users. The vulnerability requires an authenticated user to trigger the resource consumption.
    Affected if Any authenticated user accounts exist in the GitLab instance, making exploitation possible.

A GitLab installation is affected if it runs version 11.6.0 up to (but not including) 18.0.6, 18.1.4, or 18.2.2, and has at least one authenticated user who could trigger the specially crafted content processing.

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.0.6 / 18.1.4 / 18.2.2 or later
Fixed in 18.0.618.1.418.2.2
Interim mitigation

Upgrade GitLab to version 18.0.6, 18.1.4, 18.2.2 or later to remediate this vulnerability.

Recommended fix High confidence

Upgrade to GitLab 18.2.2 or later (latest stable 18.x release)

  1. 1. Create a full backup of your GitLab instance using `sudo gitlab-backup create`
  2. 2. Verify your current GitLab version with `sudo gitlab-rake gitlab:env:info`
  3. 3. Review GitLab's upgrade path documentation to plan a safe upgrade path from your current version
  4. 4. For Ubuntu/Debian: Update package index with `sudo apt-get update`
  5. 5. For Ubuntu/Debian: Install the update with `sudo apt-get install gitlab-ee` (or `gitlab-ce` for Community Edition)
  6. 6. For RHEL/CentOS: Run `sudo yum install gitlab-ee` (or `gitlab-ce`)
  7. 7. Reconfigure GitLab with `sudo gitlab-ctl reconfigure`
  8. 8. Verify the upgrade was successful by checking the version with `sudo gitlab-rake gitlab:env:info`
Caveat GitLab major/minor version upgrades may include breaking changes; review the CHANGELOG and upgrade path documentation before upgrading across multiple minor versions

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
14.0 hours of engineering $2,490
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,984.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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