Loading vulnerability…
A vulnerability in GitLab CE/EE from version 13.4 up to but not including 13.6.2 allows information disclosure through the GraphQL API, where user email addresses may be exposed unexpectedly. This occurs due to insufficient access control or filtering in the GraphQL implementation, allowing unauthorized users to retrieve email addresses of other users.
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.
What it means. What to do now. Patch path, mitigations, and the assume-compromise checklist.
What an attacker gets, and what they’ve been doing with it.
If you can’t patch tonight, do this now.
Patch, then assume compromise.
1 valid exploit after Mallory filtered fakes, detection scripts, and README-only repos.
This repository contains a Python proof-of-concept (POC) exploit for CVE-2020-26413, an information disclosure vulnerability in GitLab's GraphQL API. The main script, 'Gitlab_CVE-2020-26413.py', allows the user to test a single GitLab instance or perform bulk testing using a file of target URLs. The exploit works by sending a crafted GraphQL query to the '/api/graphql' endpoint of the target GitLab server. If the target is vulnerable, the script extracts and prints usernames and email addresses of users, and writes the results to a local file. The repository is structured simply, with the main exploit script and a README file providing usage instructions. The exploit is a POC and does not provide post-exploitation capabilities beyond information disclosure.
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.
No public activity tracked yet. Mallory keeps watching.
No public activity observed for this vulnerability.
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.