CVE-2026-4672 is an improper access control vulnerability in the GitLab Community Edition and Enterprise Edition Pipeline Test Report API. It affects GitLab CE/EE versions from 18.4 before 19.0.5, 19.1 before 19.1.3, and 19.2 before 19.2.1. Under certain conditions, the API failed to correctly enforce authorization boundaries, allowing an authenticated user holding only guest-role permissions to access pipeline test report contents that they were not authorized to view.
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.
A medium-severity improper access control vulnerability affecting the GitLab Pipeline Test Report API.
An improper access control vulnerability in the GitLab Pipeline Test Report API that could allow an authenticated guest-role user to access unauthorized test report contents.
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.