dbcve.org
GitLabApplication

CVE-2025-10858

HIGH · 7.5 CVSS v3.1 Published 2025-09-26
Fix available
A fix is available. Upgrade to 18.2.7 / 18.3.3 or later.
See remediation →
84/100
Remediation priority · High
Remotely reachable No privileges 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 was discovered in GitLab CE/EE affecting all versions before 18.2.7, 18.3 before 18.3.3, and 18.4 before 18.4.1 that allows unauthenticated users to cause a Denial of Service (DoS) condition while uploading specifically crafted large JSON 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

GitLab CE/EE versions prior to 18.2.7, 18.3.3, and 18.4.1 contain an unauthenticated denial-of-service vulnerability where attackers can trigger excessive resource consumption by uploading specially crafted large JSON files, causing service unavailability.

MitigationUpgrade GitLab to version 18.2.7, 18.3.3, 18.4.1 or later; consider implementing rate limiting or file size restrictions on unauthenticated upload endpoints as an interim control.

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.2.7>= 18.3.0, < 18.3.3= 18.4.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
None
User interaction
None
Scope
Unchanged
Confidentiality
None
Integrity
None
Availability
High

CVSS:3.1/AV:N/AC:L/PR:N/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 'gitlab-rake gitlab:version' or check the version file in the GitLab installation directory
    Affected if The version falls within < 18.2.7, >= 18.3.0 and < 18.3.3, or equals 18.4.0
  2. Verify unauthenticated access is enabled
    Check if the GitLab instance allows unauthenticated (public) access to projects or has the unrestricted API enabled
    Affected if The instance permits unauthenticated users to interact with upload or API endpoints without authentication
  3. Confirm upload endpoint is accessible to anonymous users
    Test whether the file upload endpoint accepts requests without authentication (e.g., using curl to attempt a POST request)
    Affected if Anonymous users can reach upload endpoints without being required to authenticate
  4. Check for rate limiting configuration
    Inspect GitLab's nginx configuration or GitLab's rate limiting settings in the admin area or gitlab.rb file
    Affected if No rate limiting is configured on upload endpoints, allowing unlimited requests
  5. Verify file size restrictions on uploads
    Check the maximum attachment size setting in GitLab configuration (gitlab.rb) or the nginx client_max_body_size directive
    Affected if No file size limits are enforced or limits are set excessively high for JSON uploads

The environment is affected if the installed GitLab version is vulnerable (below 18.2.7, between 18.3.0-18.3.3, or exactly 18.4.0) AND unauthenticated users can access upload endpoints without rate limiting or file 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.2.7 / 18.3.3 or later
Fixed in 18.2.718.3.3
Interim mitigation

Upgrade GitLab to version 18.2.7, 18.3.3, 18.4.1 or later; consider implementing rate limiting or file size restrictions on unauthenticated upload endpoints as an interim control.

Recommended fix High confidence

Upgrade to GitLab 18.2.7, 18.3.3, 18.4.1, or later

  1. Back up your GitLab instance data and configuration before proceeding with the upgrade
  2. Update your GitLab package repository to get the latest available packages
  3. For Debian/Ubuntu: run 'apt-get update' and 'apt-get install gitlab-ce' (or 'gitlab-ee')
  4. For RHEL/CentOS: run 'yum install gitlab-ce' (or 'gitlab-ee')
  5. Run 'sudo gitlab-ctl reconfigure' to apply the configuration changes
  6. Restart GitLab services if required: 'sudo gitlab-ctl restart'
  7. Verify the upgrade was successful by checking the GitLab version at /help or via 'gitlab-rake gitlab:env:info'
Caveat Review GitLab's release notes for any breaking changes between your current version and the target upgrade version

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
  • Testing3.0 h
  • Review / QA1.0 h
10.0 hours of engineering $1,750
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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