Cyber Resilience

CVE-2026-2619

Access Control in Gitlab 18.6.0 – 18.8.9

Access Control
Published
08 April 2026
Modified
20 July 2026
Patch / advisory
View 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:N/I:L/A:N
EPSS Score 0.0033 26th percentile
Risk Priority 35 floored blend · peak EPSS

Summary

CVE-2026-2619 is a medium-severity Incorrect Authorization (CWE-863) vulnerability in Gitlab Gitlab. Its CVSS base score is 4.3 (Medium).

Operationally, exploitation aligns with the MITRE ATT&CK technique Valid Accounts (T1078); ranked at the 26th 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.

OWASP Top 10 for Web (2025)

A01:2025 Broken Access Control

EU & UK References

Vulnerability Data

GitLab has remediated an issue in GitLab EE affecting all versions from 18.6 before 18.8.9, 18.9 before 18.9.5, and 18.10 before 18.10.3 that under certain circumstances could have allowed an authenticated user with auditor privileges to modify vulnerability flag data…

more

in private projects due to incorrect authorization.

CWE(s)
CWE-863

Related Threats

MITRE ATT&CK Enterprise TechniquesAI

T1078 Valid Accounts Stealth
Adversaries may obtain and abuse credentials of existing accounts as a means of gaining Initial Access, Persistence, Privilege Escalation, or Defense Evasion.
attack.mitre.org →
T1565.001 Stored Data Manipulation Impact
Adversaries may insert, delete, or manipulate data at rest in order to influence external outcomes or hide activity, thus threatening the integrity of the data.
attack.mitre.org →
Why these techniques?

Incorrect authorization (CWE-863) in GitLab directly allows an authenticated auditor account to perform unauthorized modification of stored vulnerability data.

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

CVEs Like This One

CVE-2026-5952Same product: Gitlab Gitlab
CVE-2024-7296Same product: Gitlab Gitlab
CVE-2025-0516Same product: Gitlab Gitlab
CVE-2026-2726Same product: Gitlab Gitlab
CVE-2025-6168Same product: Gitlab Gitlab
CVE-2023-4658Same product: Gitlab Gitlab
CVE-2026-6269Same product: Gitlab Gitlab
CVE-2023-5106Same product: Gitlab Gitlab
CVE-2023-3979Same product: Gitlab Gitlab
CVE-2023-3509Same product: Gitlab Gitlab

Affected Assets

gitlab
gitlab
18.6.0 — 18.8.9 · 18.9.0 — 18.9.5 · 18.10.0 — 18.10.3

Mitigating Controls

Control response

Prevent
Stop it (NIST 800-53)
  • AC-3 Access Enforcement
  • AC-6 Least Privilege
  • CM-5 Access Restrictions for Change
Detect
Catch it (NIST detect / respond)

—

Harden
Shrink the surface (DISA STIG)
  • 5 hardening rules · 3 OS baselines
Validate
Prove the fix (OWASP ASVS)

—

Mitigating Controls (NIST 800-53 r5) AI

AC-3 Access Enforcement good match
prevent

Directly enforces authorization checks on all access attempts, preventing an auditor from performing unauthorized modifications to vulnerability flag data.

AC-6 Least Privilege good match
prevent

Ensures auditor accounts receive only read-oriented privileges, eliminating the ability to modify vulnerability data in private projects.

CM-5 Access Restrictions for Change partial match
prevent

Restricts which roles may perform configuration or data changes, blocking modification of vulnerability flags by non-privileged accounts.

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

Defining, enforcing, and reviewing access authorizations and least privilege directly prevents incorrect authorization checks.

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.5.15 Access control partial match
prevents

Requiring consistency between access rights and classification plus formal approval steps ensures that the authorization logic correctly distinguishes between entities that should and should not be granted access.

A.5.18 Access rights partial match
prevents

Enforcing policy-driven approval and role-change reviews stops incorrect or stale authorization decisions from remaining in effect after job changes or terminations.

A.8.3 Information access restriction partial match
prevents

By tying access rights to identity, device, location and classification, the control reduces the likelihood that an authorization decision will be based on an incorrect or bypassed policy.

References