Skip to content
Tech News
← Back to articles

CISA: Hackers now exploit max severity GitLab flaw in attacks

read original get YubiKey 5 NFC Security Key → more articles
Why This Matters

A maximum-severity GitLab flaw (CVE-2026-85706) lets unauthenticated attackers read credentials and secrets from vulnerable servers in a single HTTP request, and CISA says it is already being exploited. Because GitLab is central to source code and CI/CD pipelines at more than half of the Fortune 100, a successful read of secrets could cascade into broader software supply chain compromise. Federal agencies have just three days to patch under BOD 26-04, and CISA is urging private sector defenders to move just as fast.

Key Takeaways
Worth a Look

YubiKey 5 NFC Security Key — When credential-stealing flaws like this GitLab bug hit, leaked passwords and tokens are the real prize — hardware-backed MFA makes stolen secrets far less useful. The YubiKey 5 NFC plugs into USB-A or taps via NFC and works with GitLab, GitHub, Google, and countless other accounts. It's a simple physical step toward locking down developer logins.

See YubiKey 5 NFC Security Key on Amazon → Affiliate link — we may earn a commission on purchases, at no extra cost to you. Product picked by AI based on this article; it is not a tested recommendation.

The U.S. Cybersecurity and Infrastructure Security Agency (CISA) warned that hackers are now exploiting a maximum-severity GitLab vulnerability in attacks.

GitLab's DevSecOps platform is used by over 50% of Fortune 100 companies and has over 30 million registered users worldwide.

The security flaw (tracked as CVE-2026-85706) stems from missing authentication enforcement and improper path confinement in the repository commits API, and unauthenticated attackers can exploit it to read credentials, secrets, and other sensitive information from vulnerable servers.

GitLab fixed this security issue in GitLab Community Edition (CE) and Enterprise Edition (EE) versions 19.3.2, 19.2.6, and 19.1 on Thursday, and urged users to patch their systems immediately.

While the company has yet to tag this vulnerability as actively exploited, cybersecurity firm watchTowr reported one day later that attackers were probing the Internet for GitLab servers unpatched against CVE-2026-85706.

"watchTowr Intel is already observing in-the-wild probes for the latest critical GitLab Path Traversal vulnerability, CVE-2026-85706, which allows attackers to read arbitrary files in a single HTTP request," it warned.

"Based on recent GitLab vulnerabilities, we know the time until indiscriminate exploitation is likely not far away. [..] Defenders should also hunt through log files for HTTP POST requests to '/api/v4/projects/{id}/repository/commits/' URIs containing 'file.path' parameters to identify potential exploitation attempts."

That same day, CISA added the vulnerability to its catalog of actively exploited flaws, giving government agencies three days to secure their systems under Binding Operational Directive (BOD) 26-04.

Although BOD 26-04 targets only federal agencies, CISA encouraged all network defenders, including those in the private sector, to patch their devices as soon as possible against ongoing attacks.

"These types of vulnerabilities are frequent attack vectors for malicious cyber actors and pose significant risks to the federal enterprise," it said. "While BOD 26-04 applies only to FCEB agencies, CISA encourages all organizations to adopt risk-based vulnerability management and prioritize remediation of KEV Catalog vulnerabilities."

... continue reading