Cyber Resilience

CVE-2025-1110

Access Control in Gitlab 18.0.0

Access Control
Published
22 May 2025
Modified
17 June 2026
CVSS Score v3.1 2.7
Click a component to see what it means
Raw vectorCVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:L/I:N/A:N
EPSS Score 0.0030 23th percentile
Risk Priority 25 floored blend · peak EPSS

Summary

CVE-2025-1110 is a low-severity Insufficient Granularity of Access Control (CWE-1220) vulnerability in Gitlab Gitlab. Its CVSS base score is 2.7 (Low).

Operationally, exploitation aligns with the MITRE ATT&CK technique Exploitation for Privilege Escalation (T1068); ranked at the 23th 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.

OWASP Top 10 for Web (2025)

A01:2025 Broken Access Control

EU & UK References

Vulnerability Data

An issue has been discovered in GitLab CE/EE affecting all versions from 18.0 before 18.0.1. In certain circumstances, a user with limited permissions could access Job Data via a crafted GraphQL query.

CWE(s)
CWE-1220CWE-863

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.
attack.mitre.org →
T1548 Abuse Elevation Control Mechanism Privilege Escalation
Adversaries may circumvent mechanisms designed to control privilege elevation to gain higher-level permissions.
attack.mitre.org →
T1548.002 Bypass User Account Control Privilege Escalation
Adversaries may bypass UAC mechanisms to elevate process privileges on system.
attack.mitre.org →
T1548.003 Sudo and Sudo Caching Privilege Escalation
Adversaries may perform sudo caching and/or use the sudoers file to elevate privileges.
attack.mitre.org →
T1574.010 Services File Permissions Weakness Stealth
Adversaries may execute their own malicious payloads by hijacking the binaries used by services.
attack.mitre.org →
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 →
Derived from this CVE’s CWE(s) via the direct CWE→ATT&CK cross-walk.

CVEs Like This One

CVE-2026-0934Same product: Gitlab Gitlab
CVE-2025-3396Same product: Gitlab Gitlab
CVE-2025-0765Same product: Gitlab Gitlab
CVE-2024-11669Same product: Gitlab Gitlab
CVE-2024-8116Same product: Gitlab Gitlab
CVE-2025-0652Same product: Gitlab Gitlab
CVE-2023-5009Same product: Gitlab Gitlab
CVE-2025-12555Same product: Gitlab Gitlab
CVE-2025-11340Same product: Gitlab Gitlab
CVE-2026-2619Same product: Gitlab Gitlab

Affected Assets

gitlab
gitlab
18.0.0

Mitigating Controls

Control response

Prevent
Stop it (NIST 800-53)

—

Detect
Catch it (NIST detect / respond)

—

Harden
Shrink the surface (DISA STIG)
  • 9 hardening rules · 7 OS baselines
Validate
Prove the fix (OWASP ASVS)
  • V16.4.2
  • V8.4.2
  • V11.7.1
  • V13.2.4

Mitigating Controls (NIST 800-53 r5) AI

AC-3 Access Enforcement good match

AC-3 directly requires correct enforcement of authorization decisions on every access request, structurally preventing incorrect checks.

AC-6 Least Privilege good match

Least privilege explicitly demands that only the minimum necessary accesses are granted, eliminating the broad permissions that define this weakness.

AC-24 Access Control Decisions good match

AC-24 requires access decisions to be applied precisely and unambiguously to every request, structurally blocking insufficiently granular policies.

AC-25 Reference Monitor good match

A reference monitor that is always invoked and tamper-proof forces every authorization decision through a verified, correct path.

AC-4 Information Flow Enforcement partial match

AC-4 enforces approved information flows with explicit source/destination rules, preventing overly coarse access policies from being deployed.

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.

PR.IR-01 mostly match
prevents

PR.IR-01's segmentation + zero-trust rules directly enforce minimum-necessary access at network boundaries, removing most instances of overly broad policy; CWE-1220 can still exist in application-layer or intra-segment controls that this single outcome does not address.

PR.PS-06 partial match
prevents

PR.PS-06's general SDLC practices can surface granularity issues during design/review (partial prevention) but do not specifically target access-control policy breadth, so they remove only part of CWE-1220's risk.

DE.AE-06 none match
degrades

CWE-1220 permits unauthorized access to sensitive assets but neither prevents nor impairs the delivery of adverse-event information to authorized recipients.

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.3 Information access restriction mostly match
degrades

Directly requires information-access restriction at the level of individual assets and operations, addressing the granularity gap.

A.5.15 Access control partial match
prevents

Establishes the overarching access-control policy whose granularity directly determines whether the weakness exists.

A.5.18 Access rights partial match
prevents

Defines the assignment and review of access rights; insufficient granularity in those rights is the root of CWE-1220.

A.8.2 Privileged access rights partial match
prevents

Specifies management of privileged access rights, where overly broad privileges are a common manifestation of the weakness.

A.8.18 Use of privileged utility programs none match
none

Limits use of privileged utilities; overly coarse access rules can still allow unauthorized utility access.

Hardening callouts derived

Configuration rules from DISA STIG baselines that bear on weaknesses of the type cited by this CVE. Each rule is shown with the relationship its mapping actually records, against the CWE it was authored against. Derived via CVE→CWE over `controls_xwalks` (authoritative rows only; rows rated `none` are excluded).

Oracle Linux 8 (2 rules)
  • V-248581 OL 8 must require users to provide a password for privilege escalation. prevents CWE-863
  • V-252656 The OL 8 operating system must not be configured to bypass password requirements for privilege escalation. prevents CWE-863
RHEL 7 (1 rule)
  • V-204430 The Red Hat Enterprise Linux operating system must be configured so that users must re-authenticate for privilege escalation. prevents CWE-863
RHEL 8 (1 rule)
  • V-251712 The RHEL 8 operating system must not be configured to bypass password requirements for privilege escalation. prevents CWE-863
Windows Server 2016 (1 rule)
  • V-225025 Local accounts with blank passwords must be restricted to prevent access from the network. prevents CWE-1220
Windows Server 2022 (1 rule)
  • V-254446 Windows Server 2022 must prevent local accounts with blank passwords from being used from the network. prevents CWE-1220

References