Live Exposure Defense: From CVE to Confirmed Exposure in 12 Hours – See more

Back
New CVE Detected

CVE-2026-12053 – Sensitive Information Disclosure via Duo Workflows – GitLab EE 19.1

Be the first to know when new zero-days emerge:

Subscribe to Email Alerts
Subscribe to RSS Feed

Summary

CVE-2026-12053 is a high-severity sensitive information disclosure vulnerability affecting GitLab Enterprise Edition (EE) version 19.1 prior to 19.1.1. The flaw stems from insufficient output filtering in the Duo Workflows AI feature, which under certain conditions could allow a user to access sensitive data — including source code — that had already been committed to a GitLab project. The vulnerability is classified as CVSS 8.6 (High) and was patched by GitLab on June 24, 2026.

Technical details

  • Root cause: Insufficient output filtering in GitLab EE’s Duo Workflows feature (CWE-532 — Insertion of Sensitive Information into Log File / Output). Duo Workflows, part of the GitLab Duo AI add-on, failed to adequately sanitize or restrict what data could be surfaced through its outputs.
  • Trigger conditions: The issue is exploitable under certain conditions when the Duo Workflows feature is active on a GitLab EE 19.1 instance. The vulnerability requires the Duo Workflows AI feature to be enabled (an EE-only, AI add-on capability).
  • Attack vector: Network-reachable; exploitable over HTTP/HTTPS against an internet-exposed self-managed GitLab EE 19.1 instance with Duo Workflows enabled.
  • Impact: High confidentiality impact — sensitive information (source code and committed project data) can be exposed. There is no integrity or availability impact.
  • No public proof-of-concept has been published as of June 25, 2026. The vulnerability was responsibly disclosed via HackerOne (report #3757762) by researcher 3nvz and GitLab team member Dennis Appelt.

Affected software

  • GitLab Enterprise Edition (EE): all versions from 19.1 up to (not including) 19.1.1
  • GitLab Community Edition (CE) is not affected
  • GitLab.com (SaaS) is not affected — it has already been patched
  • Only EE instances with the Duo Workflows AI feature enabled are exposed

Severity

  • CVSS v3.1 Base Score: 8.6 (High)
  • Vector String: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:N/A:N

Note: GitLab’s own patch release advisory reports a CVSS score of 7.7 with vector CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:N/A:N (Privileges Required: Low), and the vulnerability description references "a user" accessing data, which implies authentication may be required in practice. The NVD record (the authoritative source used by IONIX) scores this at 8.6 with PR:N. Customers should treat this as requiring prompt remediation regardless of which score applies.

Mitigation and recommended actions

  • Immediate: Upgrade all self-managed GitLab EE 19.1 instances to GitLab EE 19.1.1, released June 24, 2026.
  • If an immediate upgrade is not feasible, consider disabling the Duo Workflows feature on affected instances as a temporary mitigation to reduce exposure.
  • GitLab.com and instances already on 19.1.1 or later are not affected and require no action.
  • Verify your GitLab version via Admin Area → Settings → General or the GitLab API (/api/v4/version).

IONIX Status

The IONIX research team is tracking ongoing exploitation attempts and recommends immediate patching. Potentially affected assets are outlined in this post.

References

Are you exposed?

Get a free report of your organization’s exposure to this CVE and threat

  • Mapping of all Assets with this Technology
  • Identification of potentially exposed assets to this CVE
  • Confirmation of verified exploitable assets
Get Exposure Report

How IONIX’s External Exposure Management Platform Detects and Validates
Zero-Days to Shrink MTTR

1

Map your entire attack surface (continously)

IONIX uses multi-factor discovery methods, including DNS analysis, certificate mapping, metadata inspection, and more, to automatically map every internet-facing asset across your environment. This includes cloud instances, third-party platforms, shadow IT, and even forgotten infrastructure that traditional tools miss.

2

Monitor for new CVEs

Dozens of threat intel feeds using agentic technology are continuously analyzed to detect the appearance of proof-of-concept code, exploit kits, and indicators of active targeting. IONIX goes further by applying AI to proactively evaluate whether emerging vulnerabilities are likely to be exploited, even before PoCs go public.

3

Identify Potential External Exposures

Not all CVEs matter. IONIX filters vulnerabilities by asking attacker-centric questions: Can it be reached from the internet? Does it require authentication? Is it being exploited in the wild? This dramatically reduces noise and focuses teams on threats that can actually be weaponized.

4

Create Safe, Scalable Exploit Validations

IONIX transforms real-world PoCs into safe, non-intrusive test payloads that can be run in production environments without disruption. These simulations are precisely targeted to the systems that are vulnerable, ensuring rapid validation without unnecessary load.

5

Execute Exploit Validations

By combining context about software stack, versioning, exposure status, and reachability, IONIX ensures that only the right payloads are executed against the right assets, maximizing efficiency and minimizing risk.

6

Drive Fast and Actionable Remediation

Results are routed through integrations with ticketing, SOAR, and SIEM tools. Issues are written in plain language, bundled into remediation clusters, and prioritized based on asset criticality, exploitability, and blast radius. This shortens mean time to remediation (MTTR) and empowers teams to act with confidence.

Are you exposed?

Get a free report of your organization’s exposure to this CVE and threat

  • Mapping of all Assets with this Technology
  • Identification of potentially exposed assets to this CVE
  • Confirmation of verified exploitable assets
Get Exposure Report
Close

Subscribe to Threat Center RSS

Copy/paste the link below into your preferred RSS reader or follow these instructions to subscribe to Slack alerts.

Open RSS feedSlack setup instructions

Close

Get Real-Time CVE Alerts to Your Email

Be the first to know when new zero-days emerge