CVE-2026-8330 json
Insertion of Sensitive Information into Log File in GitLab
published 4mo ago modified 2mo ago also BIT-gitlab-2026-8330 , EUVD-2026-39172
- cvss
- 4.4
- version 3.1, CNA
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 0.2%
- EPSS 0.2% chance of exploitation in 30 days, percentile 9%
- public exploits
- 0
- none known
Summary
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.
Patch / fix
- bitnami gitlab 18.11.6, 19.0.3, 19.1.1
- GitLab GitLab 18.11.6, 19.0.3, 19.1.1
Is CVE-2026-8330 in your dependencies? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.
Check with FencerCISA SSVC
- Exploitation
- none
- Automatable
- no
- Technical impact
- partial
- Assessed
- 4mo ago
Exploit prediction
0.20% chance of exploitation in the next 30 days, higher than 9% of all scored CVEs (FIRST EPSS, 2026-11-11).
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| CNA | 3.1 | 4.4 | CVSS:3.1/AV:L/AC:L/PR:H/UI:N/S:U/C:H/I:N/A:N |
| OSV | 3.1 | 4.4 | CVSS:3.1/AV:L/AC:L/PR:H/UI:N/S:U/C:H/I:N/A:N |
Affected packages
| ecosystem | package | affected | fixed in |
|---|---|---|---|
| bitnami | gitlab | >=9.3.0, <18.11.6 >=19.0.0, <19.0.3 >=19.1.0, <19.1.1 |
18.11.6 19.0.3 19.1.1 |
Affected products
- GitLab GitLab
Classification
- Weakness
-
- CWE-532 Insertion of Sensitive Information into Log File
- Technology feeds
References
-
docs.gitlab.com
/releases/patches/patch-release-gitlab-19-1-1-released/
release-notes, vendor-advisory, advisory
-
gitlab.com
/gitlab-org/gitlab/-/work_items/599621
broken-link, web
-
nvd.nist.gov
/vuln/detail/CVE-2026-8330
web
Sources
- CVE List CVE-2026-8330
- NVD CVE-2026-8330
- OSV BIT-gitlab-2026-8330
Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.