Loading vulnerability…
CVE-2026-16794 is an improper authorization vulnerability in GitLab Enterprise Edition compliance framework management. Under certain conditions, an authenticated user assigned the Security Manager role can bypass intended authorization controls to execute arbitrary CI/CD jobs and access protected CI/CD variables in group projects. Affected versions are GitLab EE 18.11 through releases before 19.1.8, 19.2 through releases before 19.2.6, and 19.3 through releases before 19.3.2.
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.
1 valid exploit after Mallory filtered fakes, detection scripts, and README-only repos.
This six-file Python repository contains two command-line tools: `exploit.py`, a large offensive file-read and mass-scanning toolkit, and `safechecker.py`, a non-intrusive GitLab exposure/version and security-posture checker. `exploit.py` defines multiple encoded and normalized GitLab repository API path variants, submits file-path form fields, and parses application error bodies for content leakage. Its built-in loot list targets GitLab Rails and Omnibus secrets, database configuration, service/root SSH keys, environment variables, logs, and supporting PostgreSQL/Redis configuration. It includes target normalization, version checks, concurrent scanning, optional curl_cffi TLS impersonation, proxy and user-agent rotation, jitter/rate control, state resumption, secret-pattern matching, reports, SQLite output, and notifications. `safechecker.py` performs version-range assessment, GitLab fingerprinting, anonymous-project/security-header/TLS checks, multi-target scanning, reporting, webhook alerts, and scan diffs without attempting file reads. The repository is standalone rather than a recognized exploit framework. The claimed CVE mechanism and affected versions are represented by repository assertions; no external validation of those claims is available from the supplied contents.
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.
8 sources tracked across advisories, community write-ups, and news. New activity surfaces here as Mallory finds it.
An improper authorization vulnerability in GitLab EE compliance framework management that could permit an authenticated user holding the Security Manager role to run arbitrary CI/CD jobs and access protected group-project variables.
An improper-authorization vulnerability in GitLab EE compliance framework management. A low-privileged authenticated Security Manager could potentially execute arbitrary CI/CD jobs and access protected group-project variables.
Additional vulnerability identifier listed as addressed by the GitLab update; no technical details are provided.
A specific GitLab vulnerability addressed by the FreeBSD GitLab package security update; the content does not map this CVE to an individual flaw description.
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.