Loading vulnerability…
CVE-2026-6267 is a sensitive information exposure vulnerability in GitLab Community Edition and Enterprise Edition caused by insufficient access controls in Workhorse internal request handling. Under certain conditions, an authenticated user with the Developer role can access information they are not authorized to view. The issue affects GitLab CE/EE versions from 10.1.0 before 19.0.5, 19.1 before 19.1.3, and 19.2 before 19.2.1.
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.
No public exploits tracked yet. Mallory keeps watching.
No public exploit code observed for this vulnerability.
7 sources tracked across advisories, community write-ups, and news. New activity surfaces here as Mallory finds it.
An insufficient access control vulnerability in GitLab CE/EE that could allow an authenticated user with Developer role to access unauthorized information via internal request handling.
A sensitive information exposure vulnerability in GitLab Workhorse that could allow an authenticated Developer-role user to access unauthorized information because of insufficient access controls on internal request handling.
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.