CVE-2026-12053: Insertion of Sensitive Information into Log File in GitLab
Telemetry drift only. No threshold crossed and no authority ruling changed.
CVE record, CISA KEV and EPSS as of 2026-10-18.
CVEs like this one computed, by meaning
What to do now held facts and links
- Upgrade to 19.1.1 or later CVE record
- Record your decision, dated and frozen with today's evidence: patch by a date · mitigated by a compensating control · deferred · accepted the risk · not affected
- Check your version against the ranges this record publishes.
What it is stated by the CNA
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: Insertion of Sensitive Information into Log File
- affected
- GitLab
- published ranges
- gitlab 19.1.0
- fixed in
- 19.1.1
- fixed by package (from OSV advisories)
- gitlab (Bitnami): 19.1.1 BIT-gitlab-2026-12053
- severity
- 8.6 CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:N/A:N
- assigned by
- GitLab
- published
- 2026-06-25
check us hackerone.com gitlab.com docs.gitlab.com
Exploit code held, dated
- exploit code
- None held in the PoC-in-GitHub feed. A public repository changes this brief.
What moved held, dated
| date | EPSS | event |
|---|---|---|
| 25 Jun 2026 | 0.00328 | |
| 24 Jul 2026 | 0.00483 | |
| 4 Aug 2026 | 0.00582 | |
| 28 Aug 2026 | 0.00627 |
4 observations held. A step marked with a scoring model moved because the measurement was replaced, not because the vulnerability changed.
Outside the record researched, cited
This section reads the record's references and adds cited findings from outside it. It needs an account. Everything above is held facts and is complete without it.
What would change this brief held, dated
- CISA KEV
- Not listed in the catalogue we hold. A listing changes this brief.
- exploit probability
- 0.01 on 2026-08-28 (FIRST's EPSS, a probability and not evidence of exploitation). Next band line: 10% (0.10). Crossing a line changes this brief.
- fix
- Held: 19.1.1. A newer fix from the CNA or OSV changes this brief.
How to check this
Every value above is held with two dates: when it was true upstream (as_of) and when we recorded it (tx_from). Re-derive the exploit probability as it stood on any date:
SELECT value, source, source_version, as_of, tx_from
FROM volatile_valid_as_of('CVE-2026-12053', '2026-11-01T23:59:59.999999Z', now());