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

SSRF in GitLab CE/EE Gitaly repository import

IdentifiersCVE-2026-9204CWE-918· Server-Side Request Forgery (SSRF)

CVE-2026-9204 is a server-side request forgery vulnerability in GitLab Community Edition and Enterprise Edition affecting all versions from 18.10 before 18.10.8, 18.11 before 18.11.5, and 19.0 before 19.0.2. The flaw is in the Gitaly repository import process, where secondary URLs were insufficiently validated. Under certain conditions, an authenticated user could supply or influence repository import inputs such that the server-side import workflow accessed unintended resources. As described by GitLab, successful exploitation could allow reading arbitrary files from the Gitaly server and reaching internal network resources during repository import.

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 attacker to abuse the repository import mechanism to make unintended server-side requests from the Gitaly context. This can expose arbitrary files resident on the Gitaly server and permit access to internal network resources that are not directly reachable by the attacker. The resulting impact includes sensitive information disclosure from the Gitaly host and internal network exposure via SSRF during repository import.

Mitigation

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

If immediate patching is not possible, reduce exposure of repository import functionality to untrusted users, restrict who can perform imports, and tightly limit the Gitaly server's ability to access local files and internal network destinations through network segmentation and egress controls. Monitor and review repository import activity for anomalous secondary URL usage. These are temporary risk-reduction measures; the primary mitigation is upgrading to a fixed version.

Remediation

Patch, then assume compromise.

Upgrade GitLab CE/EE to a fixed release: 18.10.8 or later in the 18.10 series, 18.11.5 or later in the 18.11 series, or 19.0.2 or later in the 19.0 series. GitLab advised self-managed customers to upgrade immediately. GitLab.com was already patched at the time of disclosure.
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
GitLabGitalyapplication
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.