EUVD-2026-39175
GHSA-r9m9-87p7-xj9f
Severity by source
AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:L/A:N
Network-accessible IDOR requiring only authenticated low-privilege session; no availability impact; confidentiality and integrity both Low as only cleanup policy settings are exposed.
Primary rating from Vendor (gitlab).
CVSS VectorVendor: gitlab
Lifecycle Timeline
2DescriptionCVE.org
GitLab has remediated an issue in GitLab EE affecting all versions from 18.6 before 18.11.6, 19.0 before 19.0.3, and 19.1 before 19.1.1 that under certain conditions could have allowed an authenticated user to read or modify another group's virtual registry cleanup policy settings without authorization.
AnalysisAI
Authorization bypass in GitLab Enterprise Edition's virtual registry cleanup policy feature allows authenticated users to read or modify cleanup policy settings belonging to groups they do not own. Affected versions span all GitLab EE releases from 18.6 through 18.11.5, 19.0 through 19.0.2, and 19.1.0. Exploitation requires a valid GitLab EE account but no elevated privileges; no public exploit code exists and this is not in CISA KEV at time of analysis.
Technical ContextAI
The root cause is CWE-639 (Authorization Bypass Through User-Controlled Key), commonly known as an Insecure Direct Object Reference (IDOR). GitLab EE's virtual registry cleanup policy API accepts a user-controlled identifier - likely a group ID - and fails to verify that the requesting authenticated user holds the appropriate permissions for the referenced group. The virtual registry cleanup policy is a GitLab EE-specific feature governing automated cleanup of container or package registry artifacts at the group level. Because the authorization check is either absent or bypassable, an attacker who knows or enumerates a target group's identifier can issue policy read or write operations against it. The CVSS vector AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:L/A:N confirms the attack is network-accessible, low-complexity, and requires only a low-privilege authenticated session. The issue was responsibly disclosed via HackerOne (report 3628793) and remediated by GitLab.
RemediationAI
Upgrade GitLab EE to version 18.11.6, 19.0.3, or 19.1.1 as confirmed by the vendor patch release advisory at https://docs.gitlab.com/releases/patches/patch-release-gitlab-19-1-1-released/. Organizations unable to patch immediately can consider restricting network access to the GitLab API for untrusted internal segments, reducing the pool of users who can issue API requests against group-scoped registry endpoints. Disabling the virtual registry cleanup policy feature entirely, if it is not actively in use, removes the vulnerable code path - however, this trade-off should be evaluated against any active cleanup automation dependencies. Audit group-level registry cleanup policy settings after patching to detect unauthorized modifications that may have occurred before remediation. The HackerOne disclosure (https://hackerone.com/reports/3628793) and GitLab work item (https://gitlab.com/gitlab-org/gitlab/-/work_items/595468) provide additional context for internal review.
An issue has been discovered in GitLab CE/EE affecting all versions starting from 11.9. Rated critical severity (CVSS 10
An issue has been discovered in GitLab CE/EE affecting all versions from 16.1 prior to 16.1.6, 16.2 prior to 16.2.9, 16.
The SSH key upload feature (lib/gitlab_keys.rb) in gitlab-shell before 1.7.3, as used in GitLab 5.0 before 5.4.1 and 6.x
A vulnerability in GitLab CE/EE affecting all versions from 11.10 prior to 15.1.6, 15.2 to 15.2.4, 15.3 to 15.3.2 allows
The Kubernetes integration in GitLab Enterprise Edition 11.x before 11.2.8, 11.3.x before 11.3.9, and 11.4.x before 11.4
The Ruby SAML library is for implementing the client side of a SAML authorization. Rated critical severity (CVSS 9.8), t
A hardcoded password was set for accounts registered using an OmniAuth provider (e.g. Rated critical severity (CVSS 9.8)
An issue has been discovered in GitLab CE/EE affecting all versions starting from 12.10 before 14.6.5, all versions star
When requests to the internal network for webhooks are enabled, a server-side request forgery vulnerability in GitLab af
An issue has been discovered in GitLab CE/EE affecting all versions starting from 13.7.9 before 13.8.7, all versions sta
An issue was discovered in GitLab Omnibus 7.4 through 12.2.1. Rated critical severity (CVSS 9.8), this vulnerability is
An issue was discovered in GitLab Community and Enterprise Edition 9.x, 10.x, and 11.x before 11.5.8, 11.6.x before 11.6
Same technique Authentication Bypass
View allShare
External POC / Exploit Code
Leaving vuln.today