Disclaimer: This content was generated using AI. While we strive for accuracy, please verify critical information with official sources.
Sources: National Vulnerability Database, CISA KEV, Exploit-DB
CVE-2024-5318 Overview
CVE-2024-5318 is an authorization flaw in GitLab Community Edition (CE) and Enterprise Edition (EE). A Guest user can view dependency lists of private projects by accessing job artifacts. The issue affects all versions from 11.11 prior to 16.10.6, 16.11 prior to 16.11.3, and 17.0 prior to 17.0.1. The weakness maps to CWE-862: Missing Authorization.
Critical Impact
A low-privileged Guest account can enumerate dependency information for private projects, exposing software composition data that supports supply chain reconnaissance.
Affected Products
- GitLab Community Edition (CE) 11.11 through 16.10.5
- GitLab Enterprise Edition (EE) 16.11 through 16.11.2
- GitLab CE/EE 17.0.0
Discovery Timeline
- 2024-05-24 - CVE-2024-5318 published to the National Vulnerability Database (NVD)
- 2026-06-17 - Last updated in NVD database
Technical Details for CVE-2024-5318
Vulnerability Analysis
The vulnerability resides in GitLab's handling of job artifacts tied to dependency scanning. GitLab's role model restricts Guest users from reading dependency lists of private projects through the standard dependency list interface. However, the artifact access path does not enforce the same authorization check. A Guest user with access to a private project can retrieve the artifacts produced by dependency scanning jobs and parse them to reconstruct the project's dependency inventory.
This exposure reveals package names, versions, and transitive dependencies. That data supports targeted supply chain attacks, including dependency confusion and the identification of known-vulnerable components. The flaw is a confidentiality issue only; it does not alter data or disrupt availability.
Root Cause
The root cause is a missing authorization check on the artifact retrieval path for dependency scanning jobs. Role-based access control (RBAC) was applied to the dependency list view but not to the underlying artifact endpoint that exposes the same data. See GitLab Issue #427526 and the HackerOne Report #2189464 for details.
Attack Vector
Exploitation requires a Guest-level account on a private project. The attacker authenticates to the GitLab instance, locates job artifacts generated by dependency scanning pipelines, and downloads them through the web interface or REST API. No user interaction from other users is required, and the EPSS score is 0.366% (29.01 percentile) as of 2026-10-19.
No verified exploit code is published. Technical description is available in the referenced advisories.
Detection Methods for CVE-2024-5318
Indicators of Compromise
- Guest-role accounts performing repeated GET requests to /api/v4/projects/:id/jobs/:job_id/artifacts endpoints on private projects.
- Downloads of gl-dependency-scanning-report.json or similar dependency scanning artifact files by non-Developer users.
- Unusual API traffic from Guest accounts targeting pipelines across multiple private projects in a short interval.
Detection Strategies
- Audit GitLab access logs for artifact downloads correlated with user roles below Developer.
- Query the audit_events table or audit event stream for project_artifact_downloaded events tied to Guest users.
- Compare project membership roles against artifact access patterns to identify authorization drift.
Monitoring Recommendations
- Forward GitLab production logs and audit events to a centralized SIEM for role-aware correlation.
- Alert on anomalous Guest activity, particularly bulk artifact enumeration across private repositories.
- Review service account and bot tokens that hold Guest-level access on sensitive projects.
How to Mitigate CVE-2024-5318
Immediate Actions Required
- Upgrade GitLab CE/EE to version 16.10.6, 16.11.3, or 17.0.1 or later.
- Review Guest-role membership on private projects that run dependency scanning pipelines.
- Rotate any secrets that may have been exposed through artifact enumeration while vulnerable versions were deployed.
Patch Information
GitLab released fixes in versions 16.10.6, 16.11.3, and 17.0.1. The patch enforces role-based authorization on job artifact retrieval for dependency scanning outputs. Refer to GitLab Issue #427526 for the full remediation record.
Workarounds
- Restrict Guest-role assignments on private projects that use dependency scanning until patched.
- Disable dependency scanning CI jobs in projects where Guest users cannot be removed.
- Set job artifact expiration to the shortest viable interval to reduce the window for enumeration.
# Example .gitlab-ci.yml setting to reduce artifact retention
dependency_scanning:
artifacts:
expire_in: 1 hour
when: on_success
Disclaimer: This content was generated using AI. While we strive for accuracy, please verify critical information with official sources.
Sources: National Vulnerability Database, CISA KEV, Exploit-DB

