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

Denial of Service in GitLab repository archive endpoints

IdentifiersCVE-2025-13929CWE-400

GitLab CE/EE contains a denial-of-service vulnerability in repository archive endpoints affecting all versions from 10.0 before 18.7.6, 18.8 before 18.8.6, and 18.9 before 18.9.2. According to the provided advisory text, an unauthenticated attacker can issue specially crafted requests to repository archive endpoints under certain conditions and cause service disruption. The available information does not identify the exact vulnerable function or code path, but the issue is characterized as a request-handling flaw that can be triggered remotely without authentication and results in resource exhaustion or service instability at the archive endpoint layer.

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 unauthenticated remote attacker to cause denial of service against GitLab repository archive functionality. Depending on deployment characteristics and how the affected endpoint is handled, this may degrade availability of archive generation requests or contribute to broader service disruption for the GitLab instance.

Mitigation

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

If immediate patching is not possible, reduce exposure to repository archive endpoints by restricting unauthenticated access where operationally feasible, placing the instance behind rate limiting and request filtering controls, and monitoring for spikes or anomalous patterns targeting archive-related URLs. These are temporary risk-reduction measures only; the primary mitigation is to upgrade to a fixed version.

Remediation

Patch, then assume compromise.

Upgrade GitLab CE/EE to a fixed release: 18.7.6, 18.8.6, 18.9.2, or later, as appropriate for the deployed branch. GitLab.com and GitLab Dedicated are already patched according to the provided content. Self-managed administrators should apply the vendor updates immediately.
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.