Threat Intelligence

Critical GitLab Flaw Under Active Attack — Patch Immediately

The Hacker News · 21 Aug 2026

Key Takeaway If your business runs a self-managed GitLab instance, patch it now — attackers are already exploiting this flaw and delay increases your risk.

Security researchers at watchTowr have confirmed that a newly disclosed GitLab vulnerability, tracked as CVE-2026-19478, is being actively exploited only days after it was made public. Rated 9.4 out of 10 on the severity scale, the flaw is a code injection issue that lets attackers modify, delete, or rewrite data in publicly accessible GitLab projects without needing to log in or authenticate.

GitLab is widely used by development teams, including many small and medium businesses, to store and manage source code. A flaw of this severity means attackers could tamper with or destroy code repositories, potentially disrupting software projects, damaging trust in shared code, or opening the door to further attacks if malicious code is inserted unnoticed.

Because exploitation is already happening in the real world, the risk window is short. Organisations running self-managed GitLab instances should check their version against GitLab's security advisories and apply patches as a priority, rather than waiting for a routine update cycle.

GitLab vulnerability code injection

Summarised by CISO AI from The Hacker News. We link back to every original so you can read it yourself.