CVE-2026-12053 is a high-severity information disclosure vulnerability in GitLab Enterprise Edition affecting all 19.1 releases before 19.1.1. The flaw is attributed to insufficient output filtering in Duo Workflows. Under certain conditions, the vulnerable workflow output could expose sensitive information that had already been committed to a project, allowing a user to retrieve data that should not have been disclosed through that feature. The issue is remotely exploitable and impacts confidentiality rather than direct code execution or service availability.
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.
9 sources tracked across advisories, community write-ups, and news. New activity surfaces here as Mallory finds it.
A high-severity insufficient output filtering vulnerability in GitLab Duo Workflows that could allow users to access sensitive information already committed to a project.
An information disclosure vulnerability in GitLab EE caused by insufficient output filtering in Duo Workflows, potentially allowing access to sensitive information already committed to a project.
A high-severity information disclosure vulnerability in GitLab EE Duo Workflows that could expose sensitive information already committed to a project.
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.