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

Unauthenticated DoS in GitLab Duo Workflows API

IdentifiersCVE-2025-14870CWE-20

CVE-2025-14870 is a denial-of-service vulnerability in GitLab CE/EE affecting all versions from 18.5 before 18.9.7, 18.10 before 18.10.6, and 18.11 before 18.11.3. According to the provided content, the issue is caused by insufficient input validation when processing specially crafted JSON payloads in the Duo Workflows API. A remote, unauthenticated attacker can send crafted requests that trigger excessive resource consumption or otherwise destabilize the affected service, resulting in denial of service.

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 affected GitLab instances. The provided context indicates this can disrupt workflow operations and may interfere with broader GitLab functionality dependent on the affected API.

Mitigation

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

If immediate patching is not possible, reduce exposure to the Duo Workflows API by restricting network access to trusted users and systems, applying upstream rate limiting and request filtering for malformed or unexpected JSON payloads, and monitoring for spikes in anonymous requests targeting the affected API. These are temporary mitigations only; upgrading is the definitive fix.

Remediation

Patch, then assume compromise.

Upgrade self-managed GitLab CE/EE instances to a fixed release: 18.9.7, 18.10.6, 18.11.3, or later, depending on the supported upgrade path. The provided content states GitLab cloud-hosted platforms were already patched. For self-managed deployments, administrators were urged to upgrade 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 activity3

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