CVE-2025-8094 is a high-severity improper handling of permissions vulnerability in the GitLab Community Edition and Enterprise Edition project API. Under certain conditions, authenticated users with maintainer privileges could manipulate shared infrastructure resources beyond their intended access level through the project API. The flaw stems from insufficient permission enforcement in API operations governing access to shared CI/CD-related infrastructure resources, allowing a maintainer to act outside the intended authorization boundary. GitLab addressed the issue by refining permission checks within the project API to enforce proper access controls.
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.
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.
3 sources tracked across advisories, community write-ups, and news. New activity surfaces here as Mallory finds it.
A GitLab project API permission flaw that lets maintainers manipulate shared infrastructure resources beyond intended access, potentially causing denial of service to other CI/CD pipelines.
A high-severity permission-handling flaw in the GitLab project API that could let authenticated maintainers cause denial of service to other users' CI/CD pipelines.
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.