CVE-2026-12053
Received Received - Intake
Insufficient Output Filtering in GitLab EE Duo Workflows

Publication date: 2026-06-25

Last updated on: 2026-06-25

Assigner: GitLab Inc.

Description
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.
CVSS Scores
EPSS Scores
Probability:
Percentile:
Meta Information
Published
2026-06-25
Last Modified
2026-06-25
Generated
2026-06-25
AI Q&A
2026-06-25
EPSS Evaluated
N/A
NVD
CVE-2026-12053
EUVD
EUVD-2026-39169
Affected Vendors & Products
Showing 1 associated CPE
Vendor Product Version / Range
gitlab gitlab_ee From 19.1 (inc) to 19.1.1 (exc)
Helpful Resources
Exploitability
CWE
CWE Icon
KEV
KEV Icon
CWE ID Description
CWE-532 The product writes sensitive information to a log file.
Attack-Flow Graph
AI Quick Actions
Instant insights powered by AI
Executive Summary

This vulnerability in GitLab EE versions from 19.1 before 19.1.1 involves 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.

Impact Analysis

The vulnerability can lead to unauthorized access to sensitive information within a GitLab project. This means that users who should not have access might be able to view confidential data that was previously committed, potentially leading to data exposure.

Mitigation Strategies

To mitigate the vulnerability CVE-2026-12053 in GitLab EE, you should upgrade your GitLab Enterprise Edition to version 19.1.1 or later, as this version contains the fix for the issue.

Chat Assistant
Ask questions about this CVE
Hi! I’m here to help you understand CVE-2026-12053. Ask me anything about the vulnerability, its impact, or mitigation strategies.
0/70
EPSS Chart