GitLab vulnerability CVE-2026-19478 carries a CVSS 9.4 rating, letting unauthenticated attackers remotely delete or modify public projects with no login required. An emergency patch released August 17 ...

GitLab CVE-2026-19478 is under active exploitation, with unauthenticated attacks able to modify or delete public projects ...

GitLab Credits usage caps are now generally available, allowing organizations to set a monthly ceiling on agentic AI spend before it becomes an overage. Administrators can set a subscription level cap ...

Hackers started exploiting CVE-2026-19478, a critical, unauthenticated GitLab vulnerability, shortly after public disclosure.

Attackers can exploit two security vulnerabilities to manipulate or even delete project data. In a warning message, the developers assure that they have fixed versions 18.11.11, 19.0.8, 19.1.6, and 19 ...

Attacks on a recently unplanned closed vulnerability in GitLab have been observed. Attackers can, for example, delete ...

A lack of technical details could make it hard for organizations running self-managed GitLab versions to detect potential ...

Attackers don’t need credentials or user interaction to exploit the flaw which could enable supply chain attacks in self-hosted code repositories.

GitLab flaw CVE-2026-19478 is now under active exploitation, allowing unauthenticated attackers to modify or delete public ...

Broken object level authorisation, usually shortened to BOLA, is one of the most common API security issues because it sits in the gap between application logic and access control. In simple terms, ...

A critical GitLab flaw lets unauthenticated hackers modify or delete public projects and user data via GraphQL, prompting an ...

The Hacker News is the top cybersecurity news platform, delivering real-time updates, threat intelligence, data breach ...