CVE-2026-8330

MEDIUMPre-NVD 4.44.4—
EchelonGraph scoreMEDIUM confidence

Score 4.4 from GitHub Security Advisory published 2026-06-25. a secondary CVSS source baseline 4.4; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa, secondary
Trending — 3 sources updated this week
4.4EG
EchelonGraph verdictMonitorLow exploitation likelihood right now — keep watching.
  • Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS PROB: 0%CVSS: 4.4Exploit: None knownExposed: 0

No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.

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.

CVSS v3
4.4
EG Score
4.4(medium)
EG Risk
24(Track)
EG Risk 24/100SSVC: Track

EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).

How it’s computed
Severity44% × 45%
Exploitation0% × 40%
Automatability30% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
0%
EPSS %ILE
3%
KEV
Not listed

Published

June 25, 2026

Last Modified

June 26, 2026

Advisory Details (2)

Auto-updated Jun 26, 2026
No patch confirmed yet.
generic

GitLab.org / GitLab · GitLab

https://gitlab.com/gitlab-org/gitlab/-/work_items/599621
generic

GitLab Patch Release: 19.1.1, 19.0.3, 18.11.6 | GitLab Docs

https://docs.gitlab.com/releases/patches/patch-release-gitlab-19-1-1-released/

Vendor Advisories for CVE-2026-8330(2)

These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.

Weakness Classification(1)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Data Freshness Timeline

(refreshed 12× in last 7d / 58× in last 30d)

Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.

  1. 2026-07-27 13:13 UTCGHSA enrichment
  2. 2026-07-26 15:16 UTCEG score recompute
  3. 2026-07-26 15:16 UTCGHSA enrichment
  4. 2026-07-26 14:54 UTCEPSS rescore
  5. 2026-07-25 14:18 UTCEPSS rescore
  6. 2026-07-24 14:18 UTCEPSS rescore
  7. 2026-07-23 14:18 UTCEPSS rescore
  8. 2026-07-23 03:23 UTCEG score recompute
  9. 2026-07-22 14:08 UTCEPSS rescore
  10. 2026-07-21 15:25 UTCEPSS rescore
  11. 2026-07-21 15:25 UTCEPSS rescore
  12. 2026-07-20 17:08 UTCEPSS rescore
  13. 2026-07-19 14:31 UTCEPSS rescore
  14. 2026-07-19 02:29 UTCEPSS rescore
  15. 2026-07-18 10:04 UTCEPSS rescore
  16. 2026-07-16 21:26 UTCGHSA enrichment
  17. 2026-07-16 17:03 UTCEPSS rescore
  18. 2026-07-15 23:49 UTCGHSA enrichment
  19. 2026-07-15 16:57 UTCEPSS rescore
  20. 2026-07-15 02:12 UTCGHSA enrichment
  21. 2026-07-14 04:29 UTCGHSA enrichment
  22. 2026-07-13 22:31 UTCEPSS rescore
  23. 2026-07-13 06:48 UTCGHSA enrichment
  24. 2026-07-12 09:10 UTCGHSA enrichment
  25. 2026-07-12 05:46 UTCEPSS rescore
Show 39 more
  1. 2026-07-11 11:33 UTCGHSA enrichment
  2. 2026-07-11 08:27 UTCEPSS rescore
  3. 2026-07-10 13:56 UTCGHSA enrichment
  4. 2026-07-09 19:10 UTCEPSS rescore
  5. 2026-07-09 16:17 UTCGHSA enrichment
  6. 2026-07-08 18:35 UTCGHSA enrichment
  7. 2026-07-08 15:16 UTCEPSS rescore
  8. 2026-07-08 15:16 UTCEPSS rescore
  9. 2026-07-07 20:59 UTCGHSA enrichment
  10. 2026-07-07 13:46 UTCEPSS rescore
  11. 2026-07-07 13:46 UTCEPSS rescore
  12. 2026-07-06 23:21 UTCGHSA enrichment
  13. 2026-07-06 16:27 UTCEPSS rescore
  14. 2026-07-06 16:27 UTCEPSS rescore
  15. 2026-07-06 02:23 UTCEPSS rescore
  16. 2026-07-06 02:23 UTCEPSS rescore
  17. 2026-07-06 01:44 UTCGHSA enrichment
  18. 2026-07-05 04:07 UTCGHSA enrichment
  19. 2026-07-04 06:31 UTCEPSS rescore
  20. 2026-07-04 06:31 UTCEPSS rescore
  21. 2026-07-04 06:25 UTCGHSA enrichment
  22. 2026-07-03 08:43 UTCGHSA enrichment
  23. 2026-07-02 11:06 UTCGHSA enrichment
  24. 2026-07-01 15:07 UTCEPSS rescore
  25. 2026-07-01 13:30 UTCGHSA enrichment
  26. 2026-06-30 23:22 UTCEPSS rescore
  27. 2026-06-30 15:53 UTCGHSA enrichment
  28. 2026-06-29 18:14 UTCGHSA enrichment
  29. 2026-06-29 14:06 UTCEPSS rescore
  30. 2026-06-28 20:33 UTCGHSA enrichment
  31. 2026-06-28 14:07 UTCEPSS rescore
  32. 2026-06-28 04:56 UTCEPSS rescore
  33. 2026-06-27 22:56 UTCGHSA enrichment
  34. 2026-06-27 03:08 UTCEPSS rescore
  35. 2026-06-27 01:19 UTCGHSA enrichment
  36. 2026-06-26 03:43 UTCGHSA enrichment
  37. 2026-06-25 13:50 UTCEPSS rescore
  38. 2026-06-25 06:06 UTCEG score recompute
  39. 2026-06-25 06:05 UTCNVD updatefirst tracked

Related CVEs(same CWE)

Frequently asked(5)

What is CVE-2026-8330?
CVE-2026-8330 is a medium vulnerability published on June 25, 2026. 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.
When was CVE-2026-8330 disclosed?
CVE-2026-8330 was first published in the National Vulnerability Database on June 25, 2026, with the most recent update on June 26, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-8330 actively exploited?
CVE-2026-8330 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0% probability of exploitation in the next 30 days, which ranks it in the top 97.0% of all scored CVEs.
What is the CVSS score of CVE-2026-8330?
CVE-2026-8330 has a CVSS v3 base score of 4.4 (NVD).
How do I remediate CVE-2026-8330?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-8330, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

Dependency Blast Radius

Explore the affected products and dependency analysis for CVE-2026-8330

Explore →

Is Your Infrastructure Affected by CVE-2026-8330?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.

Start Free Scan →Browse All CVEs