Emerging Threats

GitLab Discloses Path Traversal Flaw Exploited in Wild

Analyst 207||Source: TheHackerNews
Modern server room with rows of equipment and a single workstation.

CVE-2026-85706, a maximum-severity (CVSS 10.0) path traversal flaw in GitLab’s repository commits API, began seeing in-the-wild probes as early as 06:00 UTC on September 11, 2026, security researchers report.

CVE-2026-85706: what the flaw is and how it works

GitLab described the root cause as "improper path confinement and missing authentication enforcement in the repository commits API." Under certain conditions, that weakness can allow an unauthenticated user to read arbitrary files from the GitLab server. The vendor scored the issue at the highest severity level — CVSS 10.0 — and issued patches to close the vector.

According to outside researchers cited in reporting, the vulnerability permits attackers to access log files and GitLab-specific configuration files that can contain credentials, secrets, and other sensitive information. Exploitation requires one concrete prerequisite: "at least one public project must exist," the head of threat intelligence at watchTowr told The Hacker News.

Affected GitLab versions and available fixes

  • All versions from 18.7 before 19.1.8
  • All versions from 19.2 before 19.2.6
  • All versions from 19.3 before 19.3.2

GitLab released patches in versions 19.3.2, 19.2.6, and 19.1.8. Organizations running self-managed GitLab instances that are exposed to the internet were urged to apply the patches immediately or to limit public access if such access is not required.

Active probes, attacker incentives, and watchTowr’s assessment

Preemptive exposure management firm watchTowr reported active in-the-wild probes since 06:00 UTC on September 11, 2026. Jake Knott, head of threat intelligence at watchTowr, framed the vulnerability as especially attractive to adversaries: "The appeal to attackers of GitLab is obvious, as unauthorized access allows an attacker to gain access to source code, CI/CD secrets, credentials, and the ability to inject code into build pipelines, gaining access or poisoning anything downstream of it, which as we've seen throughout this year has been a favorite of attackers."

Knott also placed this disclosure in immediate context: "This is the second instance of a critical severity GitLab vulnerability in recent weeks, following the previous GraphQL code injection (CVE-2026-19478) that was almost immediately actively exploited." He warned that the transition "to indiscriminate mass exploitation is likely not far away, and defenders have limited time to act."

CVE-2026-87719: companion critical fix in GitLab EE

Alongside the path traversal patch, GitLab fixed a separate critical insecure deserialization bug in GitLab Enterprise Edition tracked as CVE-2026-87719 (CVSS 9.9). GitLab described that vulnerability this way: "The vulnerability could allow an authenticated user with Duo Chat access to obtain Advanced Search instance configurations and sensitive credentials using a specially crafted GraphQL subscription argument to bypass serialization and perform server object lookup."

That bug required authentication and Duo Chat access, in contrast with CVE-2026-85706’s ability to be triggered by an unauthenticated actor under the right conditions. Both fixes were included in the same 19.x maintenance releases.

How technologists, affected enterprises, and defenders are likely to respond

  • Technologists and security teams: Apply the available patches in 19.3.2, 19.2.6, or 19.1.8 immediately for exposed self‑managed instances, or restrict public access where feasible. WatchTowr specifically advised reviewing logs for HTTP POST requests to '/api/v4/projects/{{id}}/repository/commits/' URIs containing 'file.Path' parameters to identify potential exploitation attempts.
  • Affected enterprises and procurement leaders: Prioritize patch windows for externally accessible GitLab instances and evaluate whether any public projects can be temporarily restricted, since exploitation requires at least one public project. Inventory CI/CD secrets and configuration files hosted on GitLab that could be exposed by file reads.
  • Defenders and incident responders: Treat active probes as an immediate operational signal. Given the vendor fixes and the reported rapid probing, defenders have limited time to detect and remediate attempts before broader exploitation can occur, according to watchTowr’s assessment.

The record in this episode is straightforward: a maximum-severity path traversal bug that can be triggered without authentication, active probing reported within hours of disclosure, and vendor patches that close both the unauthenticated file-read vector and a separate authenticated deserialization flaw. For organizations operating exposed, self-managed GitLab instances the decision is binary — patch now or reduce exposure — because, as the researchers warned, the window before indiscriminate mass exploitation may be short.

Source: The Hacker News — GitLab CVSS 10 File-Read Flaw Draws In-the-Wild Probes After Disclosure

Emerging ThreatsSoftware VulnerabilityAPI VulnerabilityCVSS 10.0GitlabRepository ExploitationCVE-2026-85706Path Traversal Flaw
Related Intelligence

Continue Reading

Rows of computer equipment recede into the background under fluorescent lighting.

Anthropic Disrupts China-Based AI Labs' Illicit Model Distillation Attacks

Anthropic has successfully disrupted a massive AI heist, exposing seven China-based labs that were secretly siphoning off its Claude model's capabilities to power their own AI systems. The illicit scheme involved feeding conversations between users and Anthropic's models into rival AI systems, including those from Alibaba, Xiaomi, and Moonshot.

Analyst 207
Person at desk looks concerned while on phone call with laptop and papers nearby.

Microsoft 365 Phishing Attacks Expose Data Theft Tactics

Microsoft warns that cyber attackers are using clever social engineering tactics, like impersonating IT help desks, to trick employees into spilling sensitive info and gaining access to Microsoft 365 accounts. These scammers do their homework, researching companies and staff on social media and professional networks to make their attacks convincing.

Analyst 207
Self-hosted JFrog Artifactory server in a data center with rows of computer equipment.

Artifactory Flaws Exploited to Deploy Rust Backdoor Malware

Security researchers have uncovered a sneaky attack that uses two flaws in JFrog Artifactory to deploy a custom Rust backdoor malware, giving hackers full control of self-hosted servers. This stealthy exploit chain lets attackers escalate from low privileges to admin control, even when anonymous access is disabled.

Analyst 207
Modern cybersecurity operations center with computer workstations and a blurred digital display.

Anthropic Disrupts Russian Hackers' AI-Driven Malware Rebuild Efforts

Anthropic has successfully disrupted the AI-driven malware rebuild efforts of Russian hackers, dealing a significant blow to their operations. The hackers had been using AI to refine their malware and evade detection by security defenses.

Analyst 207