dbcve.org
GitLabApplication

CVE-2025-13929

HIGH · 7.5 CVSS v3.1 Published 2026-03-11
Fix available
A fix is available. Upgrade to 18.7.6 / 18.8.6 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
GitLab has remediated an issue in GitLab CE/EE affecting all versions from 10.0 before 18.7.6, 18.8 before 18.8.6, and 18.9 before 18.9.2 that could have allowed an unauthenticated user to cause a denial of service by issuing specially crafted requests to repository archive endpoints under certain conditions.

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 unauthenticated denial of service vulnerability exists in GitLab CE/EE where specially crafted requests to repository archive endpoints can cause the service to become unavailable. The vulnerability affects all versions from 10.0 before 18.7.6, 18.8 before 18.8.6, and 18.9 before 18.9.2.

MitigationUpgrade GitLab to version 18.7.6, 18.8.6, 18.9.2 or later. If immediate upgrade is not possible, consider restricting or rate-limiting unauthenticated access to repository archive endpoints as a temporary mitigation.

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.0.0, < 18.7.6>= 18.8.0, < 18.8.6>= 18.9.0, < 18.9.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
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. Identify installed GitLab version
    Log into the GitLab admin area and navigate to the version information page, or run 'gitlab-rake gitlab:env:info' from the server terminal
    Affected if The displayed version falls within 10.0.0 to 18.7.5, 18.8.0 to 18.8.5, or 18.9.0 to 18.9.1
  2. Check project/repository visibility settings
    In GitLab admin panel, review the default project visibility setting under Admin Area > Settings > Visibility and access controls > Default project visibility
    Affected if Default visibility is set to Public or Internal, allowing unauthenticated access to repositories
  3. Verify archive endpoint accessibility
    Attempt to access a repository archive URL (for example: https://your-gitlab-instance.com/group/project/-/archive/master/project-master.zip) without providing authentication credentials
    Affected if The archive downloads or returns a valid response without requiring login
  4. Confirm unauthenticated API access
    Use a curl command to query the GitLab API without an authorization token, such as: curl -s https://your-gitlab-instance.com/api/v4/version
    Affected if The API returns valid JSON responses without authentication, indicating the instance accepts unauthenticated requests

You are affected if your GitLab version is within the vulnerable range (10.0.0 to 18.7.5, 18.8.0 to 18.8.5, or 18.9.0 to 18.9.1) AND repository archive endpoints are accessible to unauthenticated 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 18.7.6 / 18.8.6 / 18.9.2 or later
Fixed in 18.7.618.8.618.9.2
Interim mitigation

Upgrade GitLab to version 18.7.6, 18.8.6, 18.9.2 or later. If immediate upgrade is not possible, consider restricting or rate-limiting unauthenticated access to repository archive endpoints as a temporary mitigation.

Recommended fix High confidence

18.7.6, 18.8.6, or 18.9.2 (or the latest stable 18.x release)

  1. Identify the currently running GitLab version using the GitLab Rails console (gitlab-rails console) or the Admin Area UI
  2. If running a version < 18.7.6, plan upgrade to version 18.7.6 or later
  3. If running version 18.8.x, upgrade to version 18.8.6 or later
  4. If running version 18.9.x, upgrade to version 18.9.2 or later
  5. Follow the official GitLab upgrade documentation for your installation method (omnibus, source, or package manager)
  6. Ensure you have a complete backup before upgrading
  7. Test the upgrade in a staging environment before deploying to production
  8. After upgrade, verify the GitLab version matches the expected patched release
Caveat Review GitLab release notes for version-specific notes; major version jumps may require additional migration steps

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
  • Testing4.0 h
  • Review / QA2.0 h
15.0 hours of engineering $2,640
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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