Critical GitLab Flaws Let Attackers Read Arbitrary Files, Steal Credentials and Execute Code

An improper input validation flaw (CWE-863, incorrect authorization) in GitLab's environment scope pattern matcher lets an authenticated user with low privileges read CI/CD variables scoped to environments they should not have access to, under certain conditions. An attacker triggers it by crafting input that causes the pattern matcher to match outside the intended environment scope, exposing secrets such as deploy tokens, cloud credentials, or API keys stored in CI/CD variables. All self-managed GitLab CE/EE installations from 15.7 before 19.1.8, 19.2 before 19.2.6, and 19.3 before 19.3.2 are affected (GitLab's own SaaS instance is patched centrally). There is no known public proof-of-concept and the issue is not on the CISA KEV list, so exploitation is not known to be occurring, though it was disclosed alongside a GitLab security release that also covered more severe flaws.

Do: Upgrade immediately to GitLab 19.1.8, 19.2.6, or 19.3.2 (or later) depending on your minor-version track. Review audit logs for unexpected CI/CD variable reads by low-privileged users and inspect environment-scope configurations on sensitive variables. Treat any secrets stored in CI/CD variables (tokens, keys, cloud credentials) on vulnerable instances as potentially exposed to all authenticated users and rotate them as a precaution.

GitLab Community and Enterprise Editions contain an improper authorization flaw (CWE-201, insertion of sensitive information into sent data) on internal data emission endpoints, affecting all versions from 10.1.0 before 19.1.8, 19.2 before 19.2.6, and 19.3 before 19.3.2. Under certain conditions, an attacker with an authenticated account could reach these endpoints directly, bypassing the expected proxy path, and retrieve sensitive credentials and tokens exposed in the emitted data. The issue is rated medium severity (CVSS 3.1 score 5.3, confidentiality-only impact), but stolen tokens could enable follow-on compromise of accounts, CI/CD pipelines, or integrated systems. Fixes shipped in versions 19.1.8, 19.2.6, and 19.3.2. No public proof-of-concept exists, the CVE is not on CISA's KEV list, and no exploitation has been reported.

Do: Upgrade self-managed GitLab instances to 19.3.2, 19.2.6, or 19.1.8 or later immediately; GitLab.com is already patched by the vendor. After patching, rotate credentials and tokens that transit internal endpoints (CI/CD variables, runner tokens, personal/group access tokens) as a precaution. Review audit and access logs for anomalous authenticated requests to internal data emission endpoints.

CVE-2026-85706 is a path traversal flaw (CWE-35) in GitLab Community Edition and Enterprise Edition in which the repository commits API does not properly confine file paths and does not enforce authentication, allowing an unauthenticated attacker to read arbitrary files from the GitLab server. It is triggered by sending a crafted unauthenticated request to the commits API that supplies traversal sequences moving outside the intended repository path. An attacker gains the ability to read arbitrary files on the host, which can expose configuration files, certificates, and stored credentials or keys; related reporting on the recent GitLab patch wave also notes credential theft and code execution flaws, though this CVE itself is the file-read issue. All self-managed GitLab CE and EE deployments are in scope, and CISA did not publish specific affected version ranges in this data. The flaw was added to CISA's KEV catalog on 2026-09-11 and is being actively probed and exploited in the wild within a day of disclosure, with three public proof-of-concept repositories available; ransomware use is not yet confirmed.

Do: Upgrade GitLab CE/EE to the patched release identified in GitLab's security advisory (no specific fixed version number is provided in this data), prioritizing internet-facing instances in line with CISA BOD 26-04; if patching is not immediately possible, restrict exposure and review access logs for unauthenticated requests to the commits API containing path traversal sequences. Because arbitrary file read can expose server-side secrets, inventory and rotate credentials, tokens, and keys stored on or reachable by affected GitLab hosts.

GitLab EE contains a critical (CVSS 9.9) deserialization flaw (CWE-502) in which an authenticated user with Duo Chat access can pass a specially crafted GraphQL subscription argument that bypasses serialization and performs a server object lookup. Via this bypass, the attacker can obtain Advanced Search instance configurations and the sensitive credentials they contain. Because the attack requires only a low-privileged account with Duo Chat access over the network, with no user interaction, any EE deployment where Duo Chat is enabled is potentially exposed, including both self-managed instances and GitLab.com. Affected versions are EE 18.3 and later before 19.1.8, 19.2 before 19.2.6, and 19.3 before 19.3.2. No public proof-of-concept or CISA KEV listing exists for this CVE as of now, though related GitLab flaws disclosed in the same cycle are reportedly drawing internet-wide probing.

Do: Upgrade GitLab EE to 19.3.2, 19.2.6, or 19.1.8 depending on the version track in use. Until patched, restrict Duo Chat access to trusted users or disable it where feasible, and audit logs for unusual GraphQL subscription activity by authenticated Duo Chat users. After upgrading, rotate Advanced Search (Elasticsearch/OpenSearch) credentials and review search cluster configurations for signs of access.

CVE-2026-88765 is a command injection flaw (CWE-77, CVSS 3.1: 8.5 high) in GitLab Enterprise Edition that allows an authenticated user to achieve remote code execution on the GitLab server. The flaw is triggered when a specially crafted Git project export is imported and overflows the Unicode conversion buffer used during Advanced Search indexing, so it applies under certain conditions — effectively self-managed instances with Advanced Search (Elasticsearch-backed indexing) enabled. A successful attacker gains code execution with high impact to confidentiality, integrity, and availability across a changed scope, despite the modest low-privilege requirement. Affected deployments span every GitLab EE version from 12.3 up through 19.1.8, 19.2 before 19.2.6, and 19.3 before 19.3.2, with fixes available in 19.1.8, 19.2.6, and 19.3.2. There is no known public proof of concept, and the issue is not on the CISA Known Exploited Vulnerabilities catalog, so exploitation status is currently none known.

Do: Upgrade self-managed GitLab EE immediately to 19.1.8, 19.2.6, or 19.3.2 (or later), prioritizing instances with Advanced Search/Elasticsearch indexing enabled. As interim mitigations, restrict who can import projects (limit import permissions and disable project export/import where feasible) and consider disabling Advanced Search indexing if it is not required. Review audit logs and project import history for unexpected imports by low-privilege accounts and hunt for signs of code execution on affected hosts.