dbcve.org
GitLabApplication

CVE-2025-13927

HIGH · 7.5 CVSS v3.1 Published 2026-01-22
Fix available
A fix is available. Upgrade to 18.6.4 / 18.7.2 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 11.9 before 18.6.4, 18.7 before 18.7.2, and 18.8 before 18.8.2 that could have allowed an unauthenticated user to create a denial of service condition by sending crafted requests with malformed authentication data.

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 in GitLab CE/EE allows attackers to crash the application by sending crafted requests containing malformed authentication data. The vulnerability affects all versions from 11.9 through 18.6.3, 18.7.x before 18.7.2, and 18.8.x before 18.8.2.

MitigationUpgrade GitLab to version 18.6.4, 18.7.2, 18.8.2 or later to remediate this vulnerability. As this is an unauthenticated DoS, immediate patching is recommended regardless of network exposure.

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.9.0, < 18.6.4>= 18.7.0, < 18.7.2>= 18.8.0, < 18.8.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. Confirm GitLab is installed
    Check for GitLab installation by looking for /opt/gitlab directory, or run 'gitlab-rake gitlab:env:info' if GitLab is installed.
    Affected if GitLab is not installed on the system, this CVE does not apply.
  2. Determine the installed GitLab version
    Run 'gitlab-rake gitlab:env:info' and look for the 'GitLab version' line, or check /opt/gitlab/VERSION file.
    Affected if Unable to determine the version - further investigation needed.
  3. Compare version against affected ranges
    Check if the installed version falls into: 11.9.0 through 18.6.3, 18.7.0 through 18.7.1, or 18.8.0 through 18.8.1. Versions 18.6.4, 18.7.2, 18.8.2 and later are NOT affected.
    Affected if Version is within 11.9.0 to 18.6.3, OR 18.7.0 to 18.7.1, OR 18.8.0 to 18.8.1 - the system IS affected by this CVE.

The system is affected if GitLab is installed and the version falls within 11.9.0-18.6.3, 18.7.0-18.7.1, or 18.8.0-18.8.1.

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.6.4 / 18.7.2 / 18.8.2 or later
Fixed in 18.6.418.7.218.8.2
Interim mitigation

Upgrade GitLab to version 18.6.4, 18.7.2, 18.8.2 or later to remediate this vulnerability. As this is an unauthenticated DoS, immediate patching is recommended regardless of network exposure.

Recommended fix High confidence

18.8.2 (or later in the 18.8.x series, alternatively 18.6.4+ or 18.7.2+ depending on your upgrade path preference)

  1. 1. Back up your GitLab instance database and repositories before proceeding with the upgrade
  2. 2. For GitLab installations using the official omnibus packages, run: sudo apt-get update && sudo apt-get install gitlab-ce (or gitlab-ee for Enterprise Edition) to install the latest available version
  3. 3. Alternatively, for Docker deployments, pull and deploy a fixed image tag such as 18.6.4, 18.7.2, or 18.8.2 or later
  4. 4. After upgrade, verify GitLab is operational by accessing the web interface and running: sudo gitlab-rake gitlab:check
  5. 5. Monitor system logs for any unusual activity related to authentication requests
Caveat Review GitLab release notes for version-specific changes; major version jumps may require following specific upgrade paths and could introduce compatibility changes

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

Fix this in GitLab Scoped from the published advisory
  • Consultation2.0 h
  • Implementation2.0 h
  • Testing2.0 h
  • Review / QA1.0 h
7.0 hours of engineering $1,240
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,984.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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