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 13th percentile
Risk Priority 35 floored blend · peak EPSS

CVSS and EPSS are reproduced from their sources (NVD, FIRST EPSS). Risk Priority is our own derived reading, not an NVD score.

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 13th 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-24 (Access Control Decisions) and AC-25 (Reference Monitor) — 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)

Related Threats

MITRE ATT&CK Enterprise Techniques

T1068 Exploitation for Privilege Escalation Privilege Escalation
Adversaries may exploit software vulnerabilities in an attempt to elevate privileges.
T1212 Exploitation for Credential Access Credential Access
Adversaries may exploit software vulnerabilities in an attempt to collect credentials.
T1548 Abuse Elevation Control Mechanism Privilege Escalation
Adversaries may circumvent mechanisms designed to control privilege elevation to gain higher-level permissions.
Derived from this CVE’s CWE(s) via the direct CWE→ATT&CK cross-walk.

CVEs Like This One

CVE-2024-4278Same product: Gitlab Gitlab
CVE-2023-3906Same product: Gitlab Gitlab
CVE-2024-4660Same product: Gitlab Gitlab
CVE-2023-2233Same product: Gitlab Gitlab
CVE-2023-3904Same product: Gitlab Gitlab
CVE-2026-16494Same product: Gitlab Gitlab
CVE-2026-8144Same product: Gitlab Gitlab
CVE-2023-5612Same product: Gitlab Gitlab
CVE-2025-9484Same product: Gitlab Gitlab
CVE-2026-2900Same 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

Mitigating Controls (NIST 800-53 r5) AI

AC-24 requires that access-control decisions be applied to each request before the asset is reached.

AC-25 mandates a reference monitor that is always invoked before any access occurs, directly eliminating post-access checks.

AC-3 requires enforcement of access authorizations on every request, which structurally demands the check precede asset access.

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.

prevents

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

prevents

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

References