CVE-2026-11768 in GitLabinfo

Summary

by MITRE • 11/17/2026

GitLab has remediated an issue in GitLab CE/EE affecting all versions from 12.4 before 19.3.9, 19.4 before 19.4.8, and 19.5 before 19.5.6 that under certain conditions could have allowed an authenticated user to read private CI/CD job artifacts belonging to other projects through GitLab Pages due to improper validation of file paths.

Be aware that VulDB is the high quality source for vulnerability data.

Analysis

by VulDB Data Team • 11/17/2026

The vulnerability identified in GitLab represents a critical security flaw related to path traversal and insufficient input validation within the platform's artifact serving mechanism, specifically affecting versions from 12.4 up to 19.3.8, 19.4 through 19.4.7, and 19.5 through 19.5.5. This issue stems from improper validation of file paths when handling requests for GitLab Pages content that includes CI/CD job artifacts. In a typical secure implementation, the application must strictly validate any user-supplied input used to construct file system paths to ensure it remains within an intended directory boundary. However, in this instance, the logic governing how these files are served failed to adequately sanitize or canonicalize path components, allowing for the manipulation of relative references such as dot-dot-slash sequences. This technical deficiency creates a scenario where an attacker can bypass expected access controls by crafting specific HTTP requests that traverse outside the designated artifact directory structure.

From an operational perspective, this vulnerability allows authenticated users with valid credentials to read private CI/CD job artifacts belonging to other projects within the same GitLab instance or group. The impact is severe because these artifacts often contain sensitive build outputs, compiled binaries, configuration files, and potentially hardcoded secrets such as API keys, database passwords, or deployment tokens that were inadvertently included in the build process. Since the vulnerability relies on authenticated access, it does not require unauthenticated exploitation but rather a compromised account or credentials obtained through phishing or other means. Once an attacker gains authentication, they can systematically enumerate project IDs and construct malicious paths to exfiltrate data from projects they do not own, leading to significant confidentiality breaches across multiple teams or organizations sharing the GitLab instance.

This flaw aligns with Common Weakness Enumeration (CWE) category CWE-22: Improper Limitation of a Pathname to a Restricted Directory, commonly known as path traversal. It also maps to MITRE ATT&CK technique T1083: File and Directory Discovery, where adversaries search for sensitive information within the file system. The exploitation vector is classified under Network Access with Authentication required, indicating that while remote code execution or unauthenticated access is not possible, the risk of data exfiltration remains high due to the ease of crafting path traversal payloads using standard web tools. The vulnerability highlights a broader class of issues in content delivery systems where dynamic file serving mechanisms do not rigorously enforce directory boundaries against relative path manipulation.

To mitigate this risk, organizations running affected versions must upgrade GitLab immediately to version 19.3.9 or later for the 19.3 branch, version 19.4.8 or later for the 19.4 branch, and version 19.5.6 or later for the 19.5 branch. These releases contain patches that enforce stricter validation on file paths served through GitLab Pages, ensuring that requests cannot escape the intended artifact directory structure. In addition to upgrading, administrators should review access logs for unusual patterns of path traversal attempts and ensure that CI/CD pipelines are configured to avoid storing sensitive secrets in artifacts unless absolutely necessary. Implementing strict least-privilege principles for service accounts and regularly rotating any credentials found within build outputs can further reduce the blast radius if a similar vulnerability were to exist or be discovered in the future.

Responsible

GitLab

Reservation

06/09/2026

Disclosure

11/17/2026

Moderation

accepted

CPE

ready

EPSS

0.00000

KEV

no

Activities

very low

Sources

Want to stay up to date on a daily basis?

Enable the mail alert feature now!