GitLab · GitLab · published 2026-06-25
CVE-2026-12053Insertion of Sensitive Information into Log File in GitLab
Routine No exploitation evidence; EPSS 0.6%.
CVE-2026-12053 is not known to be exploited in the wild. EPSS estimates a 0.6% chance of exploitation in the next 30 days, higher than 50% of all CVEs. This GitLab vulnerability: CVSS 8.6 (v3.1), attacks can be automated. Fixed upstream in GitLab 19.1.1, 19.0.3, 18.11.6. Routine: patch when convenient.
Jump to: Remediation Exploit intelAffected versionsDescription
Remediation#
Fixed upstream in GitLab 19.1.1, 19.0.3, 18.11.6.
Patch events
DevOpsGitLab
GitLab security releases: 19.1.1, 19.0.3, 18.11.6
Upgrade to
19.1.119.0.318.11.6Why: Vendor security release for server software (most severe: CVE-2026-10086).
Exploit intelligence#
| Signal | Value | Source |
|---|---|---|
| Known exploited | No | CISA KEV |
| Ransomware use | — | CISA KEV |
| EPSS (30-day exploitation probability) | 0.6% (51th pct) | FIRST EPSS v2026.06.15 |
| CVSS base score | 8.6 (v3.1)CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:N/A:N | CNA / CISA ADP |
| SSVC exploitation | none | CISA Vulnrichment |
| SSVC automatable | Yes | CISA Vulnrichment |
| SSVC technical impact | partial | CISA Vulnrichment |
Affected versions (from the CVE record)#
- GitLab GitLab
19.1to before19.1.1(affected)
Description (from the CVE record)#
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.
Quoted from the CVE Program record.