CVE-2026-12053 Insertion of Sensitive Information into Log File in GitLab
An attacker with project access can view sensitive committed data via insufficient log filtering in Duo Workflows.
- Exploited in the wild
- Not known
- Login needed
- Not needed
- Attackable
- Over the internet
- Victim action needed
- Not needed
- Fix
- Available
What is CVE-2026-12053?
CVE-2026-12053 is a high-severity vulnerability in Gitlab Gitlab, published on 25 Jun 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.
Official 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.
Weakness: CWE-532
Which versions are affected by CVE-2026-12053?
1 open source package ship an affected version, including gitlab. It affects 1 product.
| Package | Affected | Fixed in |
|---|---|---|
gitlab Bitnami | From 19.1.0 | 19.1.1 |
Products include Gitlab Gitlab.
How do I fix CVE-2026-12053?
Upgrade gitlab to 19.1.1 or later.
Is CVE-2026-12053 being exploited?
There is no known exploitation of CVE-2026-12053 in the wild and no public exploit code.
Other vulnerabilities in Gitlab Gitlab
- CVE-2026-97229 GitLab Community Edition and Enterprise Edition Integer Overflow or Wraparound
- CVE-2026-85706 GitLab Community Edition and Enterprise Edition Path Traversal
- CVE-2023-7028 GitLab Community and Enterprise Editions Improper Access Control
- CVE-2021-22205 GitLab Community and Enterprise Editions Remote Code Execution
- CVE-2021-39935 GitLab Community and Enterprise Editions Server-Side Request Forgery (SSRF)
Sources
Also known as BIT-gitlab-2026-12053, GHSA-fwjq-556c-7hwm.