CVE-2026-12053: Insertion of Sensitive Information into Log File in GitLab
Affects gitlabSource GCVE Database
Not known to be exploited : upgrade to 19.1.1 soon.
Data as of 10 Nov 2026, 23:24 UTC
Rated by Threat Radar · No CVSS score from NVD or the CNA
- EPSS
- 0.6% chance of exploitation in 30 days – higher than 50% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
- Patch
- Available – fixed in 19.1.1
Exploitation evidence
Disclosed: evidence found.
CVE published 29 Jun 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors
A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 10 Nov 2026.
What to do
Upgrade gitlab to 19.1.1.
Affected software
| Product | Affected | Fixed in |
|---|---|---|
Bitnamigitlabpkg:bitnami/gitlabOther threats | Affected
| Fixed in
|
Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.
AI-suggested
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.
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.