BIT-gitlab-2026-12053: Insertion of Sensitive Information into Log File in GitLab
GitLab Enterprise Edition versions 19.1.0 up to but not including 19.1.1 contain a vulnerability in Duo Workflows that allows insertion of sensitive information into log files due to insufficient output filtering. This could allow users to access sensitive data previously committed to a project. The issue is fixed in version 19.1.1.
AI Analysis
Technical Summary
A vulnerability identified as CVE-2026-12053 affects GitLab Enterprise Edition versions >=19.1.0 and <19.1.1. The flaw arises from insufficient output filtering in the Duo Workflows component, which permits insertion of sensitive information into log files. This exposure could enable unauthorized users to access sensitive data that had been committed to a project. The vulnerability has been remediated in GitLab version 19.1.1.
Potential Impact
Sensitive information that was committed to a project may be exposed through log files due to improper filtering, potentially leading to unauthorized data disclosure. There are no known exploits in the wild at this time.
Mitigation Recommendations
Upgrade GitLab Enterprise Edition to version 19.1.1 or later, where this vulnerability has been fixed. No other mitigation is indicated.
BIT-gitlab-2026-12053: Insertion of Sensitive Information into Log File in GitLab
Description
GitLab Enterprise Edition versions 19.1.0 up to but not including 19.1.1 contain a vulnerability in Duo Workflows that allows insertion of sensitive information into log files due to insufficient output filtering. This could allow users to access sensitive data previously committed to a project. The issue is fixed 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
A vulnerability identified as CVE-2026-12053 affects GitLab Enterprise Edition versions >=19.1.0 and <19.1.1. The flaw arises from insufficient output filtering in the Duo Workflows component, which permits insertion of sensitive information into log files. This exposure could enable unauthorized users to access sensitive data that had been committed to a project. The vulnerability has been remediated in GitLab version 19.1.1.
Potential Impact
Sensitive information that was committed to a project may be exposed through log files due to improper filtering, potentially leading to unauthorized data disclosure. There are no known exploits in the wild at this time.
Mitigation Recommendations
Upgrade GitLab Enterprise Edition to version 19.1.1 or later, where this vulnerability has been fixed. No other mitigation is indicated.
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
- Cvss Version
- null
Threat ID: 6a42ed7427e9c79719939352
Added to database: 06/29/2026, 22:11:00 UTC
Last enriched: 07/18/2026, 12:55:59 UTC
Last updated: 08/13/2026, 13:31:28 UTC
Views: 64
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.