CVE-2026-15423 is an improper authorization vulnerability in GitLab Community Edition and Enterprise Edition affecting versions 19.0 before 19.0.6, 19.1 before 19.1.4, and 19.2 before 19.2.2. Under certain conditions, an authenticated user with developer-role permissions could execute a CI/CD pipeline on a protected branch without possessing the push permissions normally required for that branch. The flaw is caused by improper authorization in pipeline reference validation within the CI/CD pipeline API, allowing branch protection expectations to be bypassed during pipeline execution requests.
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.
6 sources tracked across advisories, community write-ups, and news. New activity surfaces here as Mallory finds it.
A high-severity authorization flaw in the GitLab CI/CD pipeline API that could allow a developer-level user to run a pipeline on a protected branch without required push permission due to improper pipeline reference validation.
A high-severity improper authorization vulnerability in the GitLab CE/EE CI/CD pipeline API that could let a developer-role user execute pipelines on protected branches without required push permissions.
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.