dbcve.org
GitLabApplication

CVE-2025-13335

MEDIUM · 6.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 →
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
GitLab has remediated an issue in GitLab CE/EE affecting all versions from 17.1 before 18.6.4, 18.7 before 18.7.2, and 18.8 before 18.8.2 that under certain circumstances could have allowed an authenticated user to create a denial of service condition by configuring malformed Wiki documents that bypass cycle detection.

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

This is a vulnerability in GitLab's Wiki functionality where authenticated users can create malformed Wiki documents that bypass cycle detection mechanisms in the parser, leading to a denial of service condition. The issue stems from insufficient validation in the Wiki document processing logic that normally prevents infinite loops or resource exhaustion from recursive document structures.

MitigationUpgrade GitLab to version 18.6.4 or higher, 18.7.2 or higher, or 18.8.2 or higher. No client-side configuration can mitigate this server-side vulnerability; patching is the only remediation.

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:>= 17.1.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
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. Identify installed GitLab version
    Run `sudo gitlab-rake gitlab:env:info` or access the GitLab admin panel and navigate to Help > Version to retrieve the exact installed version number
    Affected if Version is 17.1.0 through 18.6.3, 18.7.0 through 18.7.1, or 18.8.0 through 18.8.1
  2. Confirm Wiki feature is enabled
    Access the GitLab admin area under Settings > General > Wiki settings, or check the gitlab_rails['gitlab_wiki_enabled'] setting in /etc/gitlab/gitlab.rb for self-managed instances
    Affected if Wiki functionality is turned on in the GitLab configuration
  3. Verify authenticated user access to Wiki
    Log in as a standard authenticated user and attempt to access any project or group Wiki, or check if the instance allows authenticated user registration in Settings > Sign-up restrictions
    Affected if Authenticated users can create or edit Wiki pages within the instance

If the GitLab version is within the affected ranges AND authenticated users have the ability to create Wiki pages, the environment is vulnerable to this denial of service via malformed Wiki document parsing.

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 or higher, 18.7.2 or higher, or 18.8.2 or higher. No client-side configuration can mitigate this server-side vulnerability; patching is the only remediation.

Recommended fix High confidence

18.8.2 (or latest 18.x stable release)

  1. Identify your current GitLab installation version using `gitlab-rake gitlab:env:info`
  2. Backup your GitLab instance and database before proceeding with the upgrade
  3. Consult the GitLab upgrade path documentation for your current version to plan a safe upgrade
  4. Upgrade to version 18.8.2 (or the latest 18.x stable release) for the most complete fix
  5. Verify the upgrade was successful by checking GitLab is operational and the version matches the target

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

Fix this in GitLab Scoped from the published advisory
  • Consultation3.0 h
  • Implementation4.0 h
  • Testing3.0 h
  • Review / QA2.0 h
12.0 hours of engineering $2,130
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,408.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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