Cyber Resilience

CVE-2026-3607

Gitlab 18.3.0 – 18.9.7

Published
14 May 2026
Modified
17 June 2026
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:N/I:L/A:N
EPSS Score 0.0023 14th percentile
Risk Priority 35 floored blend · peak EPSS

Summary

CVE-2026-3607 is a medium-severity Access Control Check Implemented After Asset is Accessed (CWE-1280) vulnerability in Gitlab Gitlab. Its CVSS base score is 4.3 (Medium).

Operationally, exploitation aligns with the MITRE ATT&CK technique Exploitation for Privilege Escalation (T1068); ranked at the 14th 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-6 (Least Privilege) — see the control section below for these in your framework.

EU & UK References

Vulnerability Data

GitLab has remediated an issue in GitLab CE/EE affecting all versions from 18.3 before 18.9.7, 18.10 before 18.10.6, and 18.11 before 18.11.3 that could have allowed an authenticated user with developer-role permissions to bypass package protection rules due to improper…

more

access control.

CWE(s)
CWE-1280

Related Threats

MITRE ATT&CK Enterprise TechniquesAI

T1068 Exploitation for Privilege Escalation Privilege Escalation
Adversaries may exploit software vulnerabilities in an attempt to elevate privileges.
attack.mitre.org →
T1190 Exploit Public-Facing Application Initial Access
Adversaries may attempt to exploit a weakness in an Internet-facing host or system to initially access a network.
attack.mitre.org →
Why these techniques?

Improper access control (CWE-1280) in GitLab package protection rules directly enables privilege escalation via an authenticated developer account and exploitation of a public-facing web application.

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

CVEs Like This One

CVE-2025-9825Same product: Gitlab Gitlab
CVE-2026-5173Same product: Gitlab Gitlab
CVE-2026-4524Same product: Gitlab Gitlab
CVE-2026-1752Same product: Gitlab Gitlab
CVE-2026-1080Same product: Gitlab Gitlab
CVE-2026-1516Same product: Gitlab Gitlab
CVE-2025-2242Same product: Gitlab Gitlab
CVE-2024-9870Same product: Gitlab Gitlab
CVE-2026-0723Same product: Gitlab Gitlab
CVE-2026-12635Same product: Gitlab Gitlab

Affected Assets

gitlab
gitlab
18.3.0 — 18.9.7 · 18.3.0 — 18.9.7 · 18.10.0 — 18.10.6

Mitigating Controls

Control response

Prevent
Stop it (NIST 800-53)
  • AC-3 Access Enforcement
  • AC-6 Least Privilege
  • AC-4 Information Flow Enforcement
Detect
Catch it (NIST detect / respond)

—

Harden
Shrink the surface (DISA STIG)

—

Validate
Prove the fix (OWASP ASVS)

—

Mitigating Controls (NIST 800-53 r5) AI

AC-3 Access Enforcement good match
prevent

Directly enforces access control policies on package resources, preventing the exact developer-role bypass described in the CVE.

AC-6 Least Privilege good match
prevent

Ensures developer accounts receive only the minimum privileges required, blocking unintended access to protected packages.

AC-4 Information Flow Enforcement partial match
prevent

Enforces information flow rules between users/roles and package repositories, limiting the scope of the improper access control flaw.

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-05 mostly match
prevents

Enforcing access permissions before use directly prevents post-access checks in hardware designs.

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.

A.8.27 Secure system architecture and engineering principles partial match
prevents

Promotes secure architecture that can embed early checks, but does not mandate them.

A.8.3 Information access restriction partial match
prevents

Enforces access restrictions before asset use, directly addressing the timing flaw.

A.8.2 Privileged access rights none match
none

Limits privileged rights but does not guarantee the check precedes access.

A.8.5 Secure authentication none match
none

Strengthens authentication yet does not ensure the check occurs before asset access.

References