Cyber Resilience

CVE-2026-0602

Auth Bypass in Gitlab 15.6.0 – 18.7.6

Published
11 March 2026
Modified
17 March 2026
Patch / advisory
CVSS Score v3.1 4.3
Click a component to see what it means
Raw vectorCVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:N/A:N
EPSS Score 0.0024 16th percentile
Risk Priority 35 floored blend · peak EPSS

Summary

CVE-2026-0602 is a medium-severity Authentication Bypass Using an Alternate Path or Channel (CWE-288) vulnerability in Gitlab Gitlab. Its CVSS base score is 4.3 (Medium).

Operationally, exploitation aligns with the MITRE ATT&CK technique Data from Information Repositories (T1213); ranked at the 16th percentile by exploit likelihood (below the median); it is not currently listed in the CISA KEV catalog.

The strongest mitigations our analysis identified map to AC-3 (Access Enforcement) and AC-4 (Information Flow Enforcement) — see the control section below for these in your framework.

OWASP Top 10 for Web (2025)

EU & UK References

Vulnerability Data

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…

more

commits due to improper filtering in the snippet rendering process under certain circumstances.

CWE(s)

Related Threats

MITRE ATT&CK Enterprise TechniquesAI

T1213 Data from Information Repositories Collection
Adversaries may leverage information repositories to mine valuable information.
T1213.003 Code Repositories Collection
Adversaries may leverage code repositories to collect valuable information.
Why these techniques?

Improper access control in GitLab info repo (issues/MRs/snippets) directly enables T1213 data access from information repositories.

Confidence: HIGH · MITRE ATT&CK Enterprise v19.0

CVEs Like This One

CVE-2026-1747Same product: Gitlab Gitlab
CVE-2025-0549Same product: Gitlab Gitlab
CVE-2026-2745Same product: Gitlab Gitlab
CVE-2025-11984Same product: Gitlab Gitlab
CVE-2024-1525Same product: Gitlab Gitlab
CVE-2026-4524Same product: Gitlab Gitlab
CVE-2026-12053Same product: Gitlab Gitlab
CVE-2025-1042Same product: Gitlab Gitlab
CVE-2025-6769Same product: Gitlab Gitlab
CVE-2025-7000Same product: Gitlab Gitlab

Affected Assets

gitlab
gitlab
15.6.0 — 18.7.6 · 15.6.0 — 18.7.6 · 18.8.0 — 18.8.6

Mitigating Controls

Control response

Prevent
Stop it (NIST 800-53)
  • AC-3 Access Enforcement
  • AC-4 Information Flow Enforcement
  • SI-15 Information Output Filtering
Detect
Catch it (NIST detect / respond)

Harden
Shrink the surface (DISA STIG)
  • 7 hardening rules · 3 OS baselines
Validate
Prove the fix (OWASP ASVS)
  • V6.4.3
  • V6.6.1
  • V12.1.3

Mitigating Controls (NIST 800-53 r5) AI

prevent

Directly enforces access decisions on private issues/MRs/epics so that snippet rendering cannot bypass authorization checks and leak metadata.

prevent

Enforces information-flow rules that prevent private metadata from being released through the snippet rendering path to unauthorized authenticated users.

prevent

Applies output filtering to block unauthorized disclosure of sensitive metadata during snippet rendering.

Mitigating Controls (NIST CSF 2.0) AI

Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→CSF cross-walk (authority under review) — links open the control.

PR.AA-03 full match
prevents

Requiring authentication on every channel and path directly eliminates alternate-path bypasses.

PR.AA-05 mostly match
prevents

Enforcing authorizations and least privilege across all access vectors prevents unauthenticated alternate paths.

PR.IR-01 mostly match
prevents

Protecting networks and environments from unauthorized logical access blocks bypass via undocumented channels.

Mitigating Controls (ISO/IEC 27001:2022 Annex A) AI

Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→ISO cross-walk (authority under review) — links open the control.

detects

Security testing can detect alternate-path bypasses but does not prevent them in production.

degrades

Secure authentication control directly mitigates bypass by requiring strong, consistent authentication on all paths.

prevents

Access control policy directly addresses alternate authentication paths by requiring all channels to enforce authentication.

degrades

Authentication information management ensures credentials and mechanisms are consistently applied across all access paths.

prevents

Access rights provisioning and review prevent bypass via unmonitored or alternate channels.

prevents

Privileged access rights control reduces risk of bypass through elevated or alternate paths.

References