1-minute read
What a defender needs to know
Attackers are exploiting CVE-2026-85706, a critical GitLab flaw that lets an unauthenticated network user read arbitrary server files through the repository commits API. It affects self-managed GitLab CE and EE from 18.7 before 19.1.8, the 19.2 branch before 19.2.6, and the 19.3 branch before 19.3.2.
GitLab.com is already patched, and GitLab Dedicated customers need no action for this flaw. CISA added the vulnerability to its Known Exploited Vulnerabilities catalog on September 11 and set September 14 as the federal remediation deadline. Neither GitLab nor CISA quantifies exploitation, identifies files taken from victim systems, or publishes campaign-specific indicators.
Inventory every self-managed GitLab instance, including disaster-recovery, staging, and internal nodes, and compare the version served in production with its branch’s first fixed release: 19.1.8, 19.2.6, or 19.3.2. Retain repository commits API request records across the exposure window. Route access alone does not establish exploitation, but it preserves evidence for later triage if a reliable request pattern emerges.
The verification target is zero reachable self-managed instances below the fixed build for their branch and no load balancer sending traffic to an older node. CISA requires forensic triage under BOD-26-04 for covered federal systems. A clean runtime version inventory confirms remediation; it cannot exclude pre-patch file access without supporting request and host evidence.