CVE-2026-0602

MEDIUMNVD 4.3
4.3

GitLab has remediated an issue in GitLab CE/EE affecting all versions from 15.6 before 18.7.6, 18.8 before 18.8.6, and 18.9 before 18.9.2 that could have allowed an authenticated user to disclose metadata from private issues, merge requests, epics, milestones, or commits due to improper filtering in the snippet rendering process under certain circumstances.

CVSS v3
4.3
EG Score
EPSS
KEV
Not listed

Published

March 11, 2026

Last Modified

March 17, 2026

Vendor Advisories for CVE-2026-0602(1)

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

Frequently asked(4)

What is CVE-2026-0602?
CVE-2026-0602 is a medium vulnerability published on March 11, 2026. GitLab has remediated an issue in GitLab CE/EE affecting all versions from 15.6 before 18.7.6, 18.8 before 18.8.6, and 18.9 before 18.9.2 that could have allowed an authenticated user to disclose metadata from private issues, merge requests, epics, milestones, or commits due to improper filtering…
When was CVE-2026-0602 disclosed?
CVE-2026-0602 was first published in the National Vulnerability Database on March 11, 2026, with the most recent update on March 17, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
What is the CVSS score of CVE-2026-0602?
CVE-2026-0602 has a CVSS v3 base score of 4.3 (NVD).
How do I remediate CVE-2026-0602?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-0602, 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

See which npm, PyPI, Go, and Maven packages are affected by CVE-2026-0602

Explore →

Is Your Infrastructure Affected by CVE-2026-0602?

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