Skip to main content

CVE-2026-5954: GitLab Authorization Bypass Vulnerability

CVE-2026-5954 is an authorization bypass vulnerability in GitLab CE/EE that allows unauthorized users to download package files from public projects. This article covers technical details, affected versions, impact, and mitigation.

Published:

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-2026-5954 Overview

CVE-2026-5954 is an improper authorization vulnerability [CWE-863] in GitLab Community Edition (CE) and Enterprise Edition (EE). The flaw affects all versions from 15.1 before 19.2.8, 19.3 before 19.3.5, and 19.4 before 19.4.2. Under certain conditions, a user could download package files from a public project because authorization checks were not enforced correctly. GitLab remediated the issue in the 19.4.2 patch release.

Critical Impact

Authenticated users could retrieve package files from public projects without the authorization context the GitLab permission model is designed to enforce, leading to unintended exposure of package artifacts.

Affected Products

  • GitLab CE/EE versions 15.1 through 19.2.7
  • GitLab CE/EE versions 19.3 through 19.3.4
  • GitLab CE/EE versions 19.4 through 19.4.1

Discovery Timeline

  • 2026-10-13 - CVE-2026-5954 published to NVD
  • 2026-10-14 - Last updated in NVD database

Technical Details for CVE-2026-5954

Vulnerability Analysis

The vulnerability stems from improper authorization checks in the GitLab package registry download path. GitLab projects can host package artifacts across multiple formats, including Maven, npm, PyPI, Composer, and generic packages. Access to those artifacts should follow the project visibility and member role configuration.

In affected releases, the authorization logic did not fully evaluate the required permissions before serving package files from public projects. A user interacting with the package download endpoint could obtain files under conditions where the full policy check would normally restrict access. The impact is bounded to confidentiality and integrity of package content; availability is not affected.

Root Cause

The root cause is a missing or incorrect authorization check in the request handler that returns package files. Classified as [CWE-863] Incorrect Authorization, the handler relied on project visibility signals rather than enforcing the complete permission policy for package downloads. GitLab addressed the issue in work item GitLab Work Item #596139.

Attack Vector

Exploitation requires network access to a GitLab instance and low-privileged authenticated access. No user interaction is required, but attack complexity is high because the condition depends on specific project and package configuration states. A successful request returns package file content that the user was not intended to access. Further technical context is available in HackerOne Report #3641043.

No public proof-of-concept exploit, CISA KEV listing, or in-the-wild exploitation has been reported for CVE-2026-5954.

Detect Identity Attacks the Moment Authentication Fails

Singularity™ Identity surfaces credential misuse, lateral movement, and privilege escalation in real time, so you can contain the breach before it spreads.

Stop Identity Attacks

Detection Methods for CVE-2026-5954

Indicators of Compromise

  • Unexpected GET requests to GitLab package registry endpoints such as /api/v4/projects/:id/packages/*/files/* from users who are not members of the target project.
  • Download activity for package files from accounts that have no prior interaction history with the owning project or group.
  • Spikes in package registry traffic from a single authenticated session targeting multiple unrelated projects.

Detection Strategies

  • Review GitLab production and audit logs for package file download events and correlate requester identity against project membership and role.
  • Enable and ingest GitLab audit events into a central logging system to analyze download patterns across the GitLab instance.
  • Compare GitLab release version against 19.2.8, 19.3.5, and 19.4.2 to confirm whether a given instance remains exposed.

Monitoring Recommendations

  • Instrument alerts for abnormal rates of package download requests per user, particularly across projects where the user has no explicit role.
  • Monitor web application firewall and reverse proxy logs for enumeration patterns against /api/v4/projects/*/packages/ paths.
  • Review GitLab release notes and security advisories on an ongoing basis to track package registry authorization fixes.

How to Mitigate CVE-2026-5954

Immediate Actions Required

  • Upgrade GitLab CE/EE to version 19.4.2, 19.3.5, or 19.2.8 or later, matching the deployed release branch.
  • Audit package registry access logs since the vulnerable version was deployed to identify unauthorized downloads.
  • Rotate any secrets, tokens, or credentials embedded in package artifacts that may have been exposed to unauthorized users.

Patch Information

GitLab released fixed versions in the 19.4.2 patch release. Full remediation details are published in the GitLab Patch Release Note. The fix enforces the complete authorization policy on the package file download endpoint, aligning behavior with project visibility and member role configuration.

Workarounds

  • Restrict project visibility to Internal or Private where feasible until the patch is applied, limiting the pool of users who can reach the vulnerable endpoint.
  • Place GitLab behind a reverse proxy or API gateway and apply rate limiting on /api/v4/projects/*/packages/ paths to constrain enumeration.
  • Review and tighten GitLab role assignments to ensure only required accounts hold access to projects that host sensitive package artifacts.
bash
# Verify current GitLab version and plan upgrade
sudo gitlab-rake gitlab:env:info | grep -i "GitLab information" -A 10

# Debian/Ubuntu upgrade example (adjust package name and version to your edition)
sudo apt-get update
sudo apt-get install gitlab-ce=19.4.2-ce.0

# RHEL/CentOS upgrade example
sudo yum install gitlab-ce-19.4.2-ce.0.el8

# Validate services after upgrade
sudo gitlab-ctl reconfigure
sudo gitlab-ctl restart
sudo gitlab-rake gitlab:check SANITIZE=true

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

Experience the Most Advanced Cybersecurity Platform

See how the world’s most intelligent, autonomous cybersecurity platform can protect your organization today and into the future.