Cyber Resilience

CVE-2026-6713

Access Control in Gitlab 18.2.0 – 18.10.7

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

Summary

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

Operationally, exploitation aligns with the MITRE ATT&CK technique Exploit Public-Facing Application (T1190); ranked at the 25th 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 18.2 before 18.10.7, 18.11 before 18.11.4, and 19.0 before 19.0.1 that under certain conditions could have allowed an unauthorized user to enumerate private projects due to incorrect authorization…

more

checks.

CWE(s)

Related Threats

MITRE ATT&CK Enterprise TechniquesAI

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.
T1213.003 Code Repositories Collection
Adversaries may leverage code repositories to collect valuable information.
Why these techniques?

Authz bypass in public-facing GitLab enables project enumeration (T1190) and direct access to code repository metadata (T1213.003).

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

Likely ATT&CK TechniquesAI

Techniques this vulnerability likely enables, inferred from its description, weakness type, and attributed-actor tradecraft. Confidence is per-technique.

T1213.003 Code Repositories Collectionconfidence: HIGH
Incorrect authorization directly allows unauthorized enumeration of private GitLab projects (code repositories).
inferred from description + CWE · MITRE ATT&CK Enterprise v19.0

CVEs Like This One

CVE-2026-3553Same product: Gitlab Gitlab
CVE-2025-9957Same product: Gitlab Gitlab
CVE-2026-2726Same product: Gitlab Gitlab
CVE-2026-6269Same product: Gitlab Gitlab
CVE-2025-7736Same product: Gitlab Gitlab
CVE-2026-9807Same product: Gitlab Gitlab
CVE-2026-5377Same product: Gitlab Gitlab
CVE-2026-5796Same product: Gitlab Gitlab
CVE-2025-13928Same product: Gitlab Gitlab
CVE-2026-5952Same product: Gitlab Gitlab

Affected Assets

gitlab
gitlab
19.0.0 · 18.2.0 — 18.10.7 · 18.2.0 — 18.10.7 · 18.11.0 — 18.11.4

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)
  • 5 hardening rules · 3 OS baselines
Validate
Prove the fix (OWASP ASVS)

Mitigating Controls (NIST 800-53 r5) AI

prevent

Directly enforces approved authorizations on access requests; the CVE is caused by missing/incorrect authorization checks that allowed enumeration of private projects.

prevent

Requires users and processes to operate with the minimum necessary privileges, which would have blocked the unauthorized project enumeration described in the CVE.

prevent

Enforces policy-based control over information flows between subjects and objects, preventing the unauthorized disclosure of private project metadata.

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.

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.

prevents

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

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