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.

Published: 2026-06-25 Last update: 2026-06-26 Assigner: [email protected] Source: [email protected]
NVD Status：Analyzed，CVE State: published
View at NVD, CVE.org, EUVD

CVE-2026-8330 is rated Low Risk (18.3/100): CVSS Medium severity, with low exploitation likelihood (EPSS 0.12%). Low composite risk—no urgent action required; patch on your normal maintenance cycle and revisit priority if CVSS or EPSS increases.

Risk is dynamic; we continuously reassess and refresh what is shown on this page as upstream context changes.

Exploit prediction scoring system (EPSS) score for CVE-2026-8330

EPSS lead: Daily EPSS estimates relative likelihood of exploitation; percentile ranks this CVE among scored vulnerabilities (higher = more severe relative rank).

# Date Old EPSS score New EPSS score Delta (New - Old)
1 2026-06-25 — 0.12% —

Full EPSS history (1 record total)

Common vulnerability scoring system (CVSS) metrics for CVE-2026-8330

CVSS metrics for this CVE.

Base score Version Severity Vector Exploitability Impact Score source
4.4 3.1 MEDIUM
CVSS:3.1/AV:L/AC:L/PR:H/UI:N/S:U/C:H/I:N/A:N Click to expand
Attack vector (AV:L)
They already need access on the box, or another person has to do something wrong; it’s not a remote drive-by.
Attack complexity (AC:L)
Once they can reach the bug, pulling it off is straightforward—no weird race conditions or rare setup.
Privileges required (PR:H)
They need powerful rights—admin, root, or similar—before this pays off.
User interaction (UI:N)
Nobody has to click “OK” or open a trap file; it can work without a victim helping.
Scope (S:U)
Damage stays in the same “trust bubble” as the broken component—no big spill into unrelated systems.
Confidentiality (C:H)
Serious risk that confidential data gets exposed in a big way.
Integrity (I:N)
Data isn’t meaningfully altered or forged.
Availability (A:N)
Service keeps running; no real outage angle.
 0.8 3.6 [email protected]

Weakness enumeration for CVE-2026-8330

GitHub Security Advisory for CVE-2026-8330

GHSA-6q88-cw72-pm5w · Severity: medium — GitLab has remediated an issue in GitLab CE/EE affecting all versions from 9.3 before 18.11.6, 19...

Affected software / configurations for CVE-2026-8330

Vendor Product Version Raw CPE
gitlab gitlab >= 9.3.0, < 18.11.6 cpe:2.3:a:gitlab:gitlab:*:*:*:*:*:*:*:*
gitlab gitlab >= 19.0.0, < 19.0.3 cpe:2.3:a:gitlab:gitlab:*:*:*:*:*:*:*:*
gitlab gitlab 19.1.0 cpe:2.3:a:gitlab:gitlab:19.1.0:*:*:*:*:*:*:*

References for CVE-2026-8330

cvelogic Threat Intelligence