Skip to main content
Live Webinar with SANS (June 25)— Agentic CTI Automation for Fun & ProfitRegister Free
Mallory
Medium

Denial of Service in GitLab CE/EE Wiki Redirects

IdentifiersCVE-2025-13335CWE-835· Loop with Unreachable Exit…

CVE-2025-13335 is a denial-of-service vulnerability in GitLab Community Edition (CE) and Enterprise Edition (EE) affecting all versions from 17.1 before 18.6.4, 18.7 before 18.7.2, and 18.8 before 18.8.2. The issue is described as an infinite loop condition in Wiki redirects: under certain circumstances, an authenticated user can configure malformed Wiki documents that bypass cycle detection, causing redirect processing to loop indefinitely and resulting in a denial-of-service condition.

Share:
For your environment

Are you exposed to this one?

Mallory correlates every CVE against your assets, your vendors, and active adversary campaigns. Know which vulnerabilities matter for you, not just which ones are loud.

ANALYST BRIEF

Impact, mitigation & remediation

What it means. What to do now. Patch path, mitigations, and the assume-compromise checklist.

Impact

What an attacker gets, and what they’ve been doing with it.

Successful exploitation allows an authenticated user to degrade or disrupt GitLab availability by triggering an infinite loop in Wiki redirect handling. The documented impact is denial of service affecting the availability of the GitLab instance; no confidentiality or integrity impact is indicated in the provided material.

Mitigation

If you can’t patch tonight, do this now.

If immediate patching is not possible, reduce exposure by restricting who can create or modify Wiki content to trusted authenticated users only and monitor for malformed Wiki documents or abnormal Wiki redirect processing that could indicate exploitation. However, no specific vendor-supplied mitigation beyond upgrading was provided in the supplied content.

Remediation

Patch, then assume compromise.

Upgrade GitLab CE/EE to a fixed release. The provided advisories identify the patched versions as 18.6.4 or later for the 18.6 release line, 18.7.2 or later for the 18.7 release line, and 18.8.2 or later for the 18.8 release line. GitLab recommended that self-managed installations upgrade immediately. GitLab.com is already patched, and GitLab Dedicated customers reportedly do not need to take action.
PUBLIC EXPLOITS

Exploits

No public exploits tracked yet. Mallory keeps watching.

VALID 0 / 0 TOTALView more in app

No public exploit code observed for this vulnerability.

EXPOSURE SURFACE

Affected products & vendors

Products and vendors Mallory has correlated with this vulnerability. Open in Mallory to drill down to specific CPE configurations and version ranges.

VendorProductType
GitLabGitlabapplication

Vendor-confirmed product mapping. Mallory continuously reconciles this list against your asset inventory.

What this page doesn’t show

The version that knows your environment.

This page is what’s public. Mallory adds the parts that aren’t: which of your assets are affected, which adversaries are exploiting it right now, which detections to deploy, and what to do tonight.
Exposure mapping

Query your assets running an affected version, and investigate the blast radius.

Threat actor evidence

Every observed campaign linking this CVE to a named adversary.

Associated malware

Malware families riding this exploit, with evidence and IOCs.

Detection signatures

YARA, Sigma, Snort, and vendor rules, auto-deployed to your SIEM.

Vendor-by-vendor mapping

Cross-references every affected SKU, including bundled OEM variants.

Social activity4

Community discussion across Reddit, Mastodon, and other social sources.