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

Unauthenticated DoS in GitLab CE/EE Releases API Authorization Validation

IdentifiersCVE-2025-13928CWE-863· Incorrect Authorization

CVE-2025-13928 is a high-severity vulnerability in GitLab Community Edition (CE) and Enterprise Edition (EE) caused by incorrect authorization validation in the Releases API. GitLab states that an unauthenticated user can exploit this flaw through affected API endpoints to trigger a denial-of-service condition. The issue affects GitLab CE/EE all versions from 17.7 before 18.6.4, 18.7 before 18.7.2, and 18.8 before 18.8.2.

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 a denial-of-service condition against affected GitLab instances. Based on the provided CVSS vector (CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H), the primary impact is high availability loss, with no stated direct confidentiality or integrity impact.

Mitigation

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

If immediate patching is not possible, reduce exposure of GitLab API endpoints to untrusted networks. Practical mitigations from the provided advisory include restricting access via network ACLs or VPN, enforcing reverse-proxy allowlists, and limiting unauthenticated access paths to reduce the likelihood of unauthenticated DoS attempts.

Remediation

Patch, then assume compromise.

Upgrade GitLab CE/EE to a fixed version. The issue is remediated in GitLab 18.6.4, 18.7.2, and 18.8.2. GitLab recommends that all self-managed installations upgrade immediately. GitLab.com is already patched, and GitLab Dedicated customers 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 activity9

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