Loading vulnerability…
CVE-2026-16494 is an improper authorization vulnerability in GitLab Enterprise Edition caused by missing authorization checks on a project update endpoint in ProjectsController. Under certain conditions, an authenticated user could modify project settings that are intended to be restricted to higher-privileged roles. The flaw affects GitLab EE versions 19.1 before 19.1.4 and 19.2 before 19.2.2. The issue represents a privilege-boundary failure in project configuration management, allowing lower-privileged authenticated users to perform updates that should require elevated project permissions.
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.
5 sources tracked across advisories, community write-ups, and news. New activity surfaces here as Mallory finds it.
An authorization flaw in GitLab Enterprise Edition ProjectsController that could allow unauthorized changes to project settings normally restricted to higher-privileged roles.
A high-severity missing authorization vulnerability in GitLab EE ProjectsController that could allow an authenticated user to modify project settings reserved for higher-privileged roles.
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.