
GitLab's CVSS 10.0 Vulnerability: Why DevOps Security Can't Wait
GitLab disclosed a critical path traversal vulnerability (CVE-2026-85706) with a maximum CVSS score of 10.0, allowing unauthenticated attackers to read arbitrary files from GitLab servers through the repository commits API. The flaw affects GitLab CE and EE versions from 18.7 through 19.3.1, stemming from improper path confinement and missing authentication enforcement. Within hours of public disclosure on September 11, 2026, security researchers observed active in-the-wild exploitation attempts targeting exposed GitLab instances to extract log files, configuration data, credentials, and sensitive information. This incident highlights the accelerating timeline from vulnerability disclosure to active exploitation, particularly for DevOps platforms that house critical source code and CI/CD secrets. Following a similar pattern to the recent GitLab GraphQL injection vulnerability (CVE-2026-19478), attackers are rapidly weaponizing these flaws to compromise software supply chains and inject malicious code into build pipelines.
Kill Chain










