Incorrect Authorization in GitLab EE vulnerability flags AI detection API
GitLab EE contains an incorrect authorization flaw in the vulnerability flags AI detection API. In affected versions, under certain circumstances, an authenticated user holding auditor privileges could modify vulnerability flag data in private projects, despite not being intended to have that level of write access. The issue affects GitLab EE versions from 18.6 before 18.8.9, 18.9 before 18.9.5, and 18.10 before 18.10.3.
Are you exposed to this one?
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.
Impact, mitigation & remediation
What it means. What to do now. Patch path, mitigations, and the assume-compromise checklist.
Impact
What an attacker gets, and what they’ve been doing with it.
Mitigation
If you can’t patch tonight, do this now.
Remediation
Patch, then assume compromise.
Exploits
No public exploits tracked yet. Mallory keeps watching.
No public exploit code observed for this vulnerability.
Affected products & vendors
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.
Recent activity
5 sources tracked across advisories, community write-ups, and news. New activity surfaces here as Mallory finds it.
An incorrect authorization vulnerability in GitLab's vulnerability flags AI detection API.
A lower-severity GitLab authorization flaw that lets authenticated users with auditor privileges modify vulnerability flag data in private projects.
An incorrect authorization vulnerability in the GitLab EE vulnerability flags AI detection API that could allow an authenticated auditor to modify vulnerability flag data in private projects.
An incorrect authorization vulnerability in the GitLab EE vulnerability flags AI detection API that could let an auditor modify vulnerability flag data in private projects.
The version that knows your environment.
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.