Information Disclosure in GitLab CE/EE CSV export
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.
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.
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.
Mitigation
If you can’t patch tonight, do this now.
Remediation
Patch, then assume compromise.
Exploits
No public exploits tracked yet. Mallory keeps watching.
No public exploit code observed for this vulnerability.
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.
Vendor-confirmed product mapping. Mallory continuously reconciles this list against your asset inventory.
Recent activity
5 sources tracked across advisories, community write-ups, and news. New activity surfaces here as Mallory finds it.
An information disclosure vulnerability in GitLab through CSV export functionality.
A lower-severity GitLab authorization flaw in CSV exports that allows users to access confidential issues assigned to others.
An information disclosure vulnerability in GitLab CE/EE CSV export functionality that could allow an authenticated user to access confidential issues assigned to other users.
An information disclosure vulnerability in GitLab CSV export that could expose confidential issues assigned to other users due to insufficient authorization checks.
The version that knows your environment.
Query your assets running an affected version, and investigate the blast radius.
Every observed campaign linking this CVE to a named adversary.
Malware families riding this exploit, with evidence and IOCs.
YARA, Sigma, Snort, and vendor rules, auto-deployed to your SIEM.
Cross-references every affected SKU, including bundled OEM variants.
Community discussion across Reddit, Mastodon, and other social sources.