Critical Gitea Vulnerability CVE-2026-60004 Allows Repository Writers to Execute Commands via Git Hooks
A critical vulnerability catalogued as CVE-2026-60004 in Gitea allows a user with write permissions on a repository to execute arbitrary commands on the server hosting the platform.
The issue arises from the abuse of Git hooks, small scripts that Git can automatically launch at different stages of the development cycle and that can be turned into a vector for injecting system commands.
The key requirement is authenticated access: the attack cannot be launched by an anonymous user and instead needs an account capable of pushing changes, for example a collaborator or any role granted write permissions. This scenario occurs frequently in projects involving multiple teams, repositories shared with third parties, or environments where broad permissions are granted for convenience.
The risk becomes especially severe in organizations that rely on Gitea as part of their internal tooling. The server often maintains visibility into the corporate network, access to shared storage, and proximity to secrets that power daily operations, ranging from access tokens for repositories and container registries to CI/CD credentials and keys used in automated deployments.
The priority response consists of applying the security update; Gitea 1.27.1 is cited as the patched version. Administrators should immediately review the attack surface introduced by Git hooks, disable them if they are not essential, and restrict their use to the minimum required scope. It is also necessary to audit repositories that accept external collaborators, tighten write permissions, and inspect hook-related storage for unauthorized scripts if any anomalous activity is detected.
The existence of a publicly available proof-of-concept raises operational urgency. When a flaw already has reproducible demonstrations, the window for reaction narrows considerably. In suspected compromise scenarios, defenders should rotate credentials and tokens that the Gitea server could access, especially those linked to automation and deployments.
Related articles
N-able Releases Hotfix for Exploited N-central Authentication Bypass Flaw CVE-2026-18577
N-able has published a hotfix addressing a high-severity authentication bypass vulnerability in its N-central IT operations management platform. The flaw, tracked as CVE-2026-18577, allows attackers to bypass authentication through alternative paths or channels and potentially take over user accounts. It affects N-central 2026.1 and earlier versions and stems from an incomplete fix for the earlier CVE-2026-18556 issue. The vulnerability carries a CVSS v4.0 base score of 8.2 and is rated High severity. Exploitation has already been observed in the wild, with Indicators of Compromise including related IP addresses now publicly available. N-able released N-central 2026.3 Hotfix 1 (build 2026.3.1.7) on August 2, 2026, and urges customers to apply the update while also recommending agent updates where possible.
Adobe Releases Emergency Update for Campaign Classic Fixing Multiple Critical Vulnerabilities
Adobe has issued an urgent security update for Adobe Campaign Classic to address seven critical vulnerabilities, including several with a maximum CVSSv3.1 base score of 10.0. The flaws affect on-premises deployments on Windows and Linux as well as the on-premises components of hybrid setups. Notably, the newly released fixes also impact the previous emergency update from July 29, version 7.4.3 build 9398, requiring users to apply the latest patch immediately. Among the most severe issues are a server-side request forgery vulnerability tracked as CVE-2026-48331, an input handling flaw in the template engine identified as CVE-2026-48323, and an SQL injection vulnerability labeled CVE-2026-48330. Adobe published the corresponding security advisory on August 3, 2026, urging rapid remediation despite the short interval since the prior update.
Dark Patterns in Vulnerability Management: How Metrics Undermine Real Security
Vulnerability management programs often fail not due to lack of scanners but because of poorly chosen metrics that prioritize reporting over actual risk reduction. Teams focus on closing easy vulnerabilities, meeting CVSS-based deadlines, and improving dashboard numbers while attackers exploit the shortest path to critical assets. The article examines five common traps including total vulnerability counts, context-free SLAs, closure rate targets, static dashboards, and claims of no critical findings. It argues that these metrics create a false sense of security and distort team behavior according to Goodhart's Law. Instead, organizations should adopt attack path metrics, exposure management approaches such as CTEM, and measurements that track real reduction in attacker reachability. The piece highlights MaxPatrol Carbon as an example of tools that model attacker paths rather than isolated CVEs.
MongoDB Server Patches 24 Vulnerabilities Including Critical Flaw in mongod Compute Mode
MongoDB has released updates addressing 24 vulnerabilities in MongoDB Server, with one rated critical. The patches cover multiple branches and include fixes for CVE-2026-13072, which carries a CVSSv3.1 base score of 9.2. The critical issue affects standalone mongod instances with compute mode enabled and stems from insufficient validation of external input that can lead to memory corruption. Additional fixes resolve 16 high-severity issues, seven medium, and one low, including CVE-2026-13059 that could allow unauthorized read-write actions by low-privileged authenticated users. Updated versions MongoDB 8.3.7, 8.2.12, 8.0.28, and 7.0.39 are now available. The company published the updates on July 22, 2026, and urges immediate application to maintain system integrity.