Loading vulnerability…
CVE-2025-11702 is a high-severity improper access control vulnerability in the Runner API of GitLab Enterprise Edition. The flaw affects GitLab EE versions 17.1 before 18.3.5, 18.4 before 18.4.3, and 18.5 before 18.5.1. Insufficient authorization checks in runner-management API functionality could allow an authenticated attacker with specific project-level permissions to bypass intended project boundaries and hijack project runners associated with other projects. Because runners execute CI/CD jobs on behalf of projects, successful exploitation could let an attacker cause those runners to operate in an unauthorized project context.
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.
11 sources tracked across advisories, community write-ups, and news. New activity surfaces here as Mallory finds it.
A missing-authorization flaw in GitLab Enterprise Edition that could allow an authenticated attacker (with specific permissions) to hijack project runners belonging to other projects.
An improper access control vulnerability in the GitLab Enterprise Edition Runner API that could allow authenticated users with certain permissions to hijack runners from other projects, exposing CI/CD secrets and enabling unauthorized job execution or lateral movement.
A vulnerability listed as trending; no technical details provided in the content.
A GitLab vulnerability described as a high-severity runner hijacking flaw.
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.