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

Information Disclosure in GitLab CE/EE CSV export

IdentifiersCVE-2026-2104CWE-862

GitLab CE/EE contains an information disclosure vulnerability in CSV export functionality caused by insufficient authorization checks. In affected versions, an authenticated user could use CSV export to access data about confidential issues that were assigned to other users, even though they should not have been authorized to view those issues. The issue affects GitLab CE/EE versions from 18.2 before 18.8.9, 18.9 before 18.9.5, and 18.10 before 18.10.3.

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 unauthorized disclosure of confidential issue information through exported CSV data. An authenticated attacker could access confidential issues assigned to other users, resulting in exposure of sensitive project or workflow information that should have remained restricted.

Mitigation

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

If immediate patching is not possible, limit access to CSV export functionality to the smallest possible set of trusted users and monitor for suspicious or unnecessary issue export activity. Review permissions around confidential issues and reduce exposure of affected self-managed instances until upgrades can be applied. However, the primary mitigation is to upgrade to a fixed version.

Remediation

Patch, then assume compromise.

Upgrade GitLab CE/EE to a fixed release. GitLab remediated the issue in versions 18.8.9, 18.9.5, and 18.10.3. GitLab urged self-managed customers to upgrade immediately. GitLab.com was already patched, and GitLab Dedicated customers did 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 activity1

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