Insertion of Sensitive Information into Log File in GitLab (CVE-2026-12053)
A vulnerability in GitLab Enterprise Edition versions 19.1.0 up to but not including 19.1.1 allowed users under certain conditions to access sensitive information previously committed to a project. This was due to insufficient output filtering in Duo Workflows, which caused sensitive data to be inserted into log files. The issue has been remediated in version 19.1.1.
AI Analysis
Technical Summary
GitLab EE versions >=19.1.0 and <19.1.1 contained a vulnerability (CVE-2026-12053) where insufficient output filtering in Duo Workflows could lead to insertion of sensitive information into log files. This flaw potentially allowed users to access sensitive data already committed to a project. The vulnerability was addressed and fixed in version 19.1.1.
Potential Impact
Users of affected GitLab EE versions could have accessed sensitive information committed to projects due to the logging of such data without proper filtering. This exposure could lead to unauthorized disclosure of sensitive project information.
Mitigation Recommendations
Upgrade GitLab EE to version 19.1.1 or later, where this vulnerability has been fixed. Since a patch is available and the issue is remediated, applying the official fix is the recommended action.
Insertion of Sensitive Information into Log File in GitLab (CVE-2026-12053)
Description
A vulnerability in GitLab Enterprise Edition versions 19.1.0 up to but not including 19.1.1 allowed users under certain conditions to access sensitive information previously committed to a project. This was due to insufficient output filtering in Duo Workflows, which caused sensitive data to be inserted into log files. The issue has been remediated in version 19.1.1.
Affected software
Run on your own infrastructure? Check whether these packages are installed with threat-finder — our free open-source scanner.
AI-Powered Analysis
Machine-generated threat intelligence
Technical Analysis
GitLab EE versions >=19.1.0 and <19.1.1 contained a vulnerability (CVE-2026-12053) where insufficient output filtering in Duo Workflows could lead to insertion of sensitive information into log files. This flaw potentially allowed users to access sensitive data already committed to a project. The vulnerability was addressed and fixed in version 19.1.1.
Potential Impact
Users of affected GitLab EE versions could have accessed sensitive information committed to projects due to the logging of such data without proper filtering. This exposure could lead to unauthorized disclosure of sensitive project information.
Mitigation Recommendations
Upgrade GitLab EE to version 19.1.1 or later, where this vulnerability has been fixed. Since a patch is available and the issue is remediated, applying the official fix is the recommended action.
Technical Details
- Gcve Source
- db.gcve.eu
- Osv Id
- BIT-gitlab-2026-12053
- Osv Schema Version
- 1.6.2
- Aliases
- ["CVE-2026-12053"]
- Ecosystems
- ["Bitnami"]
- Database Specific Severity
- High
Threat ID: 6a42ed7427e9c79719939352
Added to database: 06/29/2026, 22:11:00 UTC
Last enriched: 09/10/2026, 23:03:03 UTC
Last updated: 09/28/2026, 01:47:40 UTC
Views: 116
Community Reviews
0 reviewsCrowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.
Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.
Actions
Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.
Need more coverage?
Upgrade to Pro Console for AI refresh and higher limits.
For incident response and remediation, OffSeq services can help resolve threats faster.
Latest Threats
Check if your credentials are on the dark web
Instant breach scanning across billions of leaked records. Free tier available.