Information Disclosure in GitLab EE Duo Workflows
CVE-2026-12053 is a high-severity information disclosure vulnerability in GitLab Enterprise Edition (EE) affecting version 19.1 before 19.1.1. According to the provided content, the issue is caused by insufficient output filtering in Duo Workflows. Under certain conditions, this flaw could allow a user to access sensitive information that had already been committed to a project. The available information does not identify a specific vulnerable function or code path beyond Duo Workflows output handling/filtering.
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
7 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.
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.