EUVD-2026-50484
GHSA-6fhj-cgmm-xfx6
Severity by source
AV:N/AC:H/PR:L/UI:N/S:C/C:H/I:H/A:H
Developer-role auth gives PR:L; 'under certain conditions' internal handling gives AC:H; scope change to other resources S:C; impact is primarily unauthorized information access (C:H), with limited integrity and no clear availability effect.
Primary rating from Vendor (GitLab).
CVSS VectorVendor: GitLab
CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:C/C:H/I:H/A:H
Lifecycle Timeline
3DescriptionCVE.org
GitLab has remediated an issue in GitLab CE/EE affecting all versions from 10.1.0 before 19.0.5, 19.1 before 19.1.3, and 19.2 before 19.2.1 that under certain conditions could have allowed an authenticated user with Developer role to access unauthorized information due to insufficient access controls on internal request handling.
Articles & Coverage 2
AnalysisAI
Information disclosure in GitLab CE/EE (all versions from 10.1.0 before 19.0.5, 19.1 before 19.1.3, and 19.2 before 19.2.1) allows an authenticated user holding only the Developer role to reach unauthorized information because internal request handling enforces insufficient access controls (CWE-201). Publicly available exploit code exists (referenced HackerOne report #3658324), but there is no public exploit identified as being used in active attacks. …
Unlock full vulnerability intelligence
- Risk assessment & exploitation conditions
- Attack chain visualization
- Remediation with exact patch versions
- Threat intelligence from 22 sources
- Personal watchlist & email alerts
Free forever · No credit card required
Attack ChainAIDerived
Hypothetical attack flow derived from CVE metadata
Vulnerability AssessmentAI
| Exploitation | Exploitation requires an authenticated account with at least the Developer role on the target GitLab instance/project (PR:L), so it is not remotely reachable by anonymous users despite AV:N. … Additional conditions and limiting factors are described in the full assessment. |
| Risk Assessment | The CVSS 3.1 vector (AV:N/AC:H/PR:L/UI:N/S:C/C:H/I:H/A:H = 8.5) tells a nuanced story: network-reachable and requiring only low privileges (a Developer account, which is common and widely granted in GitLab projects), but with high attack complexity (AC:H) and a scope change (S:C) that lifts the score. … Full risk analysis with EPSS, KEV, and SSVC signal comparison available after sign-in. |
| Exploit Scenario | An attacker who has (or phishes/compromises) a low-privilege Developer account on a GitLab project crafts requests that exercise the flawed internal request-handling path, causing GitLab to return information the account should not be authorized to see. Because a public POC exists (HackerOne #3658324), a motivated insider or credential-theft actor could reproduce the technique, though the high attack complexity means it may require specific project or instance conditions to succeed. |
| Remediation | Vendor-released patch: upgrade to GitLab 19.0.5, 19.1.3, or 19.2.1 (or later) depending on your current major/minor branch, as documented at https://docs.gitlab.com/releases/patches/patch-release-gitlab-19-2-1-released/; self-managed operators should apply the corresponding patch release for their branch immediately. … Detailed patch versions, workarounds, and compensating controls in full report. |
Recommended ActionAI
Within 24 hours, inventory all GitLab instances and identify those running versions before 19.0.5, 19.1.3, or 19.2.1, then review access logs for suspicious developer activity and restrict developer access to sensitive projects where feasible. …
Sign in for detailed remediation steps and compensating controls.
Threat intelligence, references, and detailed analysis are available after sign-in.
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