CVE-2026-8330 Insertion of Sensitive Information into Log File in GitLab
Attackers can read sensitive information from application logs due to insufficient filtering in a CI/CD API endpoint in GitLab.
- Exploited in the wild
- Not known
- Login needed
- An administrator
- Attackable
- Local or same network only
- Victim action needed
- Not needed
- Fix
- Available
What is CVE-2026-8330?
CVE-2026-8330 is a medium-severity vulnerability in Gitlab Gitlab, published on 25 Jun 2026. It can only be exploited from the same machine or local network, with no action from the victim.
Official 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.
Weakness: CWE-532
Which versions are affected by CVE-2026-8330?
1 open source package ship an affected version, including gitlab. It affects 1 product.
| Package | Affected | Fixed in |
|---|---|---|
gitlab Bitnami | From 9.3.0 | 18.11.6, 19.0.3, 19.1.1 |
Products include Gitlab Gitlab.
How do I fix CVE-2026-8330?
Upgrade gitlab to a fixed version for your release line: 18.11.6, 19.0.3 or 19.1.1.
Is CVE-2026-8330 being exploited?
There is no known exploitation of CVE-2026-8330 in the wild and no public exploit code.
Other vulnerabilities in Gitlab Gitlab
- CVE-2026-97229 GitLab Community Edition and Enterprise Edition Integer Overflow or Wraparound
- CVE-2026-85706 GitLab Community Edition and Enterprise Edition Path Traversal
- CVE-2023-7028 GitLab Community and Enterprise Editions Improper Access Control
- CVE-2021-22205 GitLab Community and Enterprise Editions Remote Code Execution
- CVE-2021-39935 GitLab Community and Enterprise Editions Server-Side Request Forgery (SSRF)
Sources
Also known as BIT-gitlab-2026-8330, GHSA-6q88-cw72-pm5w.