CVE-2026-12053: Insertion of Sensitive Information into Log File in GitLab
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.
Affected Software
Remediation
Recommended actions to resolve this vulnerability, in priority order.
- Upgrade
Upgrade
GitLab EEto a version that resolves this vulnerability.Fixed in 19.1.1
Event History
Frequently Asked Questions
What is the severity of CVE-2026-12053?
The severity of CVE-2026-12053 is high with a score of 8.6.
How do I fix CVE-2026-12053?
To fix CVE-2026-12053, update GitLab EE to version 19.1.1 or later.
What types of information are affected by CVE-2026-12053?
CVE-2026-12053 can expose sensitive information that may have been previously committed to a project.
In what versions is CVE-2026-12053 applicable?
CVE-2026-12053 affects all GitLab EE versions from 19.1 before 19.1.1.
What conditions trigger CVE-2026-12053?
CVE-2026-12053 occurs under certain conditions due to insufficient output filtering in Duo Workflows.