CVE-2026-8330: Insertion of Sensitive Information into Log File in 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.
Affected Software
Remediation
Recommended actions to resolve this vulnerability, in priority order.
- Upgrade
Upgrade to a fixed release to a version that resolves this vulnerability.
Fixed in 18.11.6 - Upgrade
Upgrade to a fixed release to a version that resolves this vulnerability.
Fixed in 19.0.3 - Upgrade
Upgrade to a fixed release to a version that resolves this vulnerability.
Fixed in 19.1.1
Event History
Frequently Asked Questions
What is the severity of CVE-2026-8330?
CVE-2026-8330 has a severity rating of medium, with a score of 4.4.
How do I fix CVE-2026-8330?
Fix CVE-2026-8330 by updating GitLab to the latest version beyond 18.11.6, 19.0.3, or 19.1.1.
What versions of GitLab are affected by CVE-2026-8330?
CVE-2026-8330 affects all GitLab CE/EE versions from 9.3 before 18.11.6, 19.0 before 19.0.3, and 19.1 before 19.1.1.
What type of vulnerability is CVE-2026-8330?
CVE-2026-8330 is an insertion of sensitive information into log files due to insufficient filtering in a CI/CD API endpoint.
What are the potential impacts of CVE-2026-8330?
The potential impact of CVE-2026-8330 includes the exposure of sensitive information through application logs.