Vulnerability record · CVE-2026-8330 · published 25 June 2026
CVE-2026-8330: Gitlab sensitive information in log file vulnerability
Gitlab · Gitlab
GitLab has remediated an issue in GitLab CE/EE affecting all versions from 9.3 before 18.11.6, 19.0 before 19.0.3, and 19.1 before 19.1.1 that under certain conditions could have allowed sensitive information to be written to application logs due to insufficient filtering in a CI/CD API endpoint.
Description
GitLab has remediated an issue in GitLab CE/EE affecting all versions from 9.3 before 18.11.6, 19.0 before 19.0.3, and 19.1 before 19.1.1 that under certain conditions could have allowed sensitive information to be written to application logs due to insufficient filtering in a CI/CD API endpoint.
CVSS:3.1/AV:L/AC:L/PR:H/UI:N/S:U/C:H/I:N/A:N
Affected products
1 vulnerable configurations from NVD's CPE data, grouped by vendor and product.
References
| Link | Tags |
|---|---|
| https://docs.gitlab.com/releases/patches/patch-release-gitlab-19-1-1-released/ | Release NotesVendor Advisory |
| https://gitlab.com/gitlab-org/gitlab/-/work_items/599621 | Broken Link |
Track CVE-2026-8330 inside VULONE
Watch it alongside the ransomware crews, C2 infrastructure and forum chatter that reference it, query it through the API and pull it into your SIEM over TAXII.
Related vulnerabilities
Same products first, then exploited flaws of the same weakness class.
Source: NIST National Vulnerability Database (record CVE-2026-8330), CISA KEV, FIRST EPSS (scores of 2026-09-29). This page is refreshed as NVD updates the record.