Skip to main content
Meet us at Black Hat USA 2026— Las Vegas, August 1–6Book a Meeting
Mallory
HighCISA KEVExploited in the wildPublic exploit

GitLab CE/EE Server-Side Request Forgery via CI Lint API

IdentifiersCVE-2021-39935CWE-918· Server-Side Request Forgery (SSRF)

CVE-2021-39935 is a server-side request forgery (SSRF) vulnerability in GitLab Community Edition and Enterprise Edition. It affects all versions starting from 10.5 before 14.3.6, all versions starting from 14.4 before 14.4.4, and all versions starting from 14.5 before 14.5.2. The issue is in the CI Lint API, where unauthorized external users could cause the GitLab server to perform server-side requests. In environments where external users should not have access to this functionality, the flaw allows abuse of the CI Lint API to induce outbound requests from the GitLab instance to attacker-specified destinations, including potentially internal services reachable only from the server.

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 unauthorized external user to leverage the GitLab server as an SSRF primitive. This can expose internal network services, cloud instance metadata endpoints, and other resources reachable from the GitLab host but not directly accessible to the attacker. Depending on network topology and reachable services, impact can include internal reconnaissance, access to sensitive metadata or tokens, and pivoting toward additional compromise of adjacent systems or trusted internal services.

Mitigation

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

If immediate patching is not possible, restrict access to the CI Lint API to trusted users and networks only, such as through reverse proxy controls, WAF rules, or network ACLs. Additionally, reduce the GitLab instance’s outbound network reachability to limit access to internal services and cloud metadata endpoints, and monitor for suspicious CI Lint API usage and anomalous outbound requests from the GitLab server.

Remediation

Patch, then assume compromise.

Upgrade GitLab CE/EE to a fixed release. The vulnerable ranges are fixed in 14.3.6, 14.4.4, and 14.5.2. Systems running affected versions should be updated to the appropriate patched version or a later supported release in the relevant branch.
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 signatures1

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 activity17

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