CVE-2026-12053

Insertion of Sensitive Information into Log File in GitLab

No known exploitation. EPSS puts it in the 48th percentile. A vendor fix is available.

CVSS 3.18.6High EPSS percentile48th0.6% chance in 30 days CISA KEVNot listedNo confirmed exploitation
No public exploit known FixVendor fixNo build named by the sources

Published 2026-06-25Updated 2026-06-26Sources: CVE.org, NVD

NVD CVE.org

What to do

The vendor has published a fix. Version details are below where the sources state them.

Steps

Written by AI from the record

Check your GitLab edition/version and confirm you are running GitLab EE before 19.1.1.
If you’re below 19.1.1, plan an upgrade immediately.
Upgrade GitLab to 19.1.1 or above.

Vendor advisory Usually a quick update

Check it yourselfA free OpenVAS check exists for this CVE. Run it against your hosts.Is your organisation exposed?Request an assessment to establish which checks fit your systems.

What it is

From the CVE record

GitLab has remediated an issue in GitLab EE affecting all versions from 19.1 before 19.1.1 that under certain conditions could have allowed a user to access sensitive information that had already been committed to a project, due to insufficient output filtering in Duo Workflows.

In plain language

Written by AI from the record

GitLab could have leaked sensitive information from already-published project content into logs, and you should update if you’re on a vulnerable GitLab version.

In GitLab EE versions before 19.1.1, insufficient filtering in Duo Workflows could cause sensitive information that was already committed to a project to be inserted into log files (network-accessible, no authentication required per the finding).

If you're affected

Sensitive data exposure from projects
Account or customer data leakage
Compliance and audit impact
Incident response costs

What is it

This bug is like a “printer” that accidentally includes private text in the job log. If the wrong kind of workflow output makes it into the logs, someone could read sensitive information that was already stored in the project. Even though the information existed in the project, the logs make it easier to access it in ways it shouldn’t be.

Who is affected

This matters if your business uses GitLab EE and you can trigger or access Duo Workflows in your environment. The finding indicates no authentication or user interaction is required, and the attack can be done over the network; however, reachability in the default configuration is not confirmed in the findings. Treat this as relevant if your GitLab is exposed to the network and Duo Workflows are enabled/configured so the vulnerable behavior can be reached.

How urgent is it

This should be treated as urgent patching because it’s a high-severity information exposure issue and GitLab has already released a fix. There’s no confirmed KEV listing and no public exploit code noted, so this is not “already widespread,” but the safest move is to upgrade now to eliminate the risk.

What to do — in detail

Confirm whether you’re affected

Determine your GitLab edition and version (GitLab EE vs other editions matters for this finding).
If you are running GitLab EE before 19.1.1, you are in the affected range described by the patch finding.

Upgrade (recommended)

Upgrade to GitLab 19.1.1 or above.
Use GitLab’s patch release guidance for 19.1.1 from the referenced release documentation.

Temporary workaround (if you can’t patch immediately)

Not enough information is provided in the findings to name a reliable, specific configuration-only mitigation for Duo Workflows logging/filtering.
If an upgrade cannot be done right away, reduce the chance the vulnerable path is reachable by limiting external network exposure to GitLab and restricting who/what can interact with Duo Workflows.

What to monitor after updating

Look for recent job/workflow log entries related to Duo Workflows and verify they no longer contain sensitive content.
Check whether any log systems (central logging/retention) captured sensitive data during the window before you upgraded, and follow your normal incident/compliance procedures if needed.

Due date

No CISA KEV due date is provided in the findings (CVE-2026-12053 is not listed in CISA KEV).

Technical context

Severity is high (CVSS 8.6) with the reported impact focused on confidentiality. The weakness is CWE-532 (Insertion of Sensitive Information into Log File). Mechanism: insufficient output filtering in Duo Workflows can insert sensitive information (already committed to a project) into log output that can be accessed by an attacker. The finding states the vulnerability is network-accessible, with authentication and user interaction marked as none; however, whether it’s reachable in default configuration is not determined. Exploitation status: not listed in CISA KEV and no clear dated press exploitation claim; no public exploit code is on record; EPSS is predicted low with a flat trend (do not treat as proof of safety). Patch availability: fixed in 19.1.1.

This is a general assessment based on public vulnerability data. It does not account for your specific infrastructure — when in doubt, consult a security specialist.

Exploitation

Where each signal puts this CVE on the scale from published to confirmed exploited.

EPSS48th

CISA KEV

Not in the catalog. CISA has not confirmed exploitation.

Public exploits

No public exploit or proof of concept found in the sources we track.

EPSS

0.6% chance of exploitation activity in the next 30 days, which ranks it in the 48th percentile of scored CVEs.

Exploit Prediction Scoring System, FIRST.org. A probability, not a confirmation.

Lifecycle

6 events over 6 days, from the signal feeds we watch.

2026-07-01OpenVAS check added
2026-06-26Patch availablerecord updated
2026-06-25Publishedweakness classified, att&ck mapped

Affected products

GitLabcommercial · NLaka gitlab ce/ee
- GitLabWeb AppSaaSDevTools & CI / ci-cd

And 1 more affected product. See all after sign-in

Technical detail

CVSS 3.1 vector

Open in the CVSS calculator

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:N/A:N

Scored 8.6 by NVD.

How it is reached

Attack Vector NetworkExploitable remotely over the network without any special conditions
Attack Complexity LowNo special conditions — the attack can be reliably reproduced
Privileges Required NoneNo authentication required — anyone can exploit this
User Interaction NoneNo user interaction needed — fully automated exploitation

Scope

Scope ChangedThe exploit can affect other components (e.g. sandbox escape, host compromise from VM)

Impact if exploited

Confidentiality HighTotal information disclosure — all data in the component is compromised
Integrity NoneNo integrity impact
Availability NoneNo availability impact