dbcve.org
GitLabApplication

CVE-2025-7337

MEDIUM · 6.5 CVSS v3.1 Published 2025-09-12
Fix available
A fix is available. Upgrade to 18.1.6 / 18.2.6 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 7.8 before 18.1.6, 18.2 before 18.2.6, and 18.3 before 18.3.2 that could have allowed an authenticated user with Developer-level access to cause a persistent denial of service affecting all users on a GitLab instance by uploading large files.

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 CE/EE allows authenticated users with Developer-level access to upload large files that consume excessive system resources, causing persistent denial of service for all users on the instance. The vulnerability stems from insufficient controls on file upload size and resource consumption in affected versions.

MitigationUpgrade GitLab to version 18.1.6, 18.2.6, 18.3.2 or later. Additionally, implement file size limits on uploads and monitor for anomalous upload patterns as compensating controls until patching is complete.

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:>= 7.8.0, < 18.1.6>= 18.2.0, < 18.2.6>= 18.3.0, < 18.3.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. Determine installed GitLab version
    Run `sudo gitlab-rake gitlab:env:info` or check the GitLab admin area under /admin/about to find the exact version number
    Affected if The installed version is >= 7.8.0 and < 18.1.6, OR >= 18.2.0 and < 18.2.6, OR >= 18.3.0 and < 18.3.2
  2. Verify Developer role exists
    Check GitLab admin settings at /admin/roles or inspect group/project member roles to confirm Developer-level access exists for any users
    Affected if Any users have Developer-level permissions in the GitLab instance
  3. Confirm file upload is enabled
    Check if projects/repositories have upload functionality enabled. This is typically enabled by default for projects where users can commit files via the web interface or API
    Affected if Projects allow authenticated users to upload files through the web UI, API, or repository upload features
  4. Inspect file size limits configuration
    Check GitLab configuration files (gitlab.rb or gitlab.yml) for `max_attachment_size` or `max_file_size` settings. Also verify in Admin Area > Settings > Preferences > File uploads
    Affected if No file size limit is configured, or the configured limit is excessively large or missing entirely

The environment is affected if the installed GitLab version falls within the affected ranges AND Developer-level authenticated users can upload files without adequate size restrictions.

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.1.6 / 18.2.6 / 18.3.2 or later
Fixed in 18.1.618.2.618.3.2
Interim mitigation

Upgrade GitLab to version 18.1.6, 18.2.6, 18.3.2 or later. Additionally, implement file size limits on uploads and monitor for anomalous upload patterns as compensating controls until patching is complete.

Recommended fix Moderate confidence

GitLab 18.1.6, 18.2.6, 18.3.2, or later (preferably 18.3.2 or later stable release)

  1. Back up your GitLab instance database and repositories before upgrading
  2. Review GitLab upgrade documentation for your current version to ensure compatibility
  3. Plan for downtime as GitLab upgrades typically require service interruption
  4. For package installations (Omnibus), run: sudo gitlab-ctl stop && sudo gitlab-rake gitlab:backup:create
  5. Upgrade to GitLab 18.1.6, 18.2.6, 18.3.2, or a later stable version (preferably 18.3.2 or later)
  6. For Omnibus: sudo apt-get update && sudo apt-get install gitlab-ce (or gitlab-ee) or download the appropriate package from GitLab's downloads page
  7. After installation, run: sudo gitlab-ctl reconfigure
  8. Start GitLab: sudo gitlab-ctl start
Caveat GitLab major version upgrades may require database migrations and can have breaking changes; review the Changelog for between-version differences before upgrading

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

Fix this in GitLab Scoped from the published advisory
  • Consultation1.0 h
  • Implementation2.0 h
  • Testing2.0 h
  • Review / QA1.0 h
6.0 hours of engineering $1,040
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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