CVE-2026-8330
Insertion of Sensitive Information into Log File in GitLab
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.
INFO
Published Date :
June 25, 2026, 4:34 a.m.
Last Modified :
June 25, 2026, 4:34 a.m.
Remotely Exploit :
No
Source :
GitLab
Affected Products
The following products are affected by CVE-2026-8330
vulnerability.
Even if cvefeed.io is aware of the exact versions of the
products
that
are
affected, the information is not represented in the table below.
No affected product recoded yet
CVSS Scores
| Score | Version | Severity | Vector | Exploitability Score | Impact Score | Source |
|---|---|---|---|---|---|---|
| CVSS 3.1 | MEDIUM | ceab7361-8a18-47b1-92ba-4d7d25f6715a | ||||
| CVSS 3.1 | MEDIUM | [email protected] |
Solution
- Update GitLab to version 18.11.6 or later.
- Update GitLab to version 19.0.3 or later.
- Update GitLab to version 19.1.1 or later.
We scan GitHub repositories to detect new proof-of-concept exploits. Following list is a collection of public exploits and proof-of-concepts, which have been published on GitHub (sorted by the most recently updated).
Results are limited to the first 15 repositories due to potential performance issues.
The following list is the news that have been mention
CVE-2026-8330 vulnerability anywhere in the article.