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
Automating Asset Scanning in MaxPatrol VM via API: Part 4 on Authentication
A detailed technical guide explains how to build asset scanning automation in MaxPatrol VM using its API, starting with authentication methods. The author covers three authorization options including local account login-password, domain account credentials, and reference tokens, providing working Python examples for local accounts. Code reads secrets from an .env file and obtains a Bearer token valid for 24 hours from the Core role instance. The post details required privileges in both the Management Console and MaxPatrol 10 for tasks such as vulnerability exports, dynamic asset group management, scan task creation, and report exporting. It credits Alexey Leonov for an early GitHub script that enabled practical API usage and lists additional resources including webinars, SDK, CLI, Jira integration, and a Postman collection. All subsequent API calls rely on the generated headers containing the Bearer token.
Securing Hadoop Clusters: Removing Passwords from XML Configs with Credential Provider API and JCEKS
Hadoop configurations frequently expose sensitive credentials such as database passwords and cloud access keys in plain text within files like hive-site.xml and core-site.xml. The Credential Provider API, introduced in Hadoop 2.6, allows applications to retrieve secrets from an external JCEKS keystore instead of embedding them directly in XML. This mechanism uses conf.getPassword() to fetch decrypted values from the keystore when hadoop.security.credential.provider.path is configured. JCEKS relies on the outdated PBEWithMD5AndTripleDES algorithm, which remains vulnerable to Sweet32 attacks in theory though practical risk for small keystore files is low. Master password protection for the keystore itself is the weakest link, with options including environment variables, protected password files, or HDFS Transparent Data Encryption. Arenadata has automated credential encryption management in its ADH platform through ADCM to handle keystore creation, permission setting, and rotation across cluster nodes.
CISA Adds Five Exploited Vulnerabilities to KEV Catalog Including AhsayCBS Authentication and Command Injection Flaws
The US Cybersecurity and Infrastructure Security Agency (CISA) has added five vulnerabilities to its Known Exploited Vulnerabilities catalog after confirming active exploitation in the wild. Four vulnerabilities were registered on October 14, 2026, and one additional entry followed on October 15. Among the newly listed issues are two critical flaws affecting the AhsayCBS backup management server: CVE-2026-105133, an authentication bypass in the API, and CVE-2026-105134, a command injection vulnerability in the replication feature. When chained together, the pair allows unauthenticated remote attackers to execute arbitrary operating system commands. Vendor Ahsay has released hotfixes in versions 10.3.4.45 and 9.15.2.70 because standard patches cannot fully address the issues. The advisory also references vulnerabilities in Atlassian products and multiple network security solutions from other vendors.
Google Issues Chrome Security Update Fixing Critical Vulnerability Two Days After Previous Patch
Google has released a new set of security updates for its Chrome browser that address ten vulnerabilities, including one rated critical. The update arrives just two days after a larger patch that fixed 37 issues on October 13. The most severe flaw, tracked as CVE-2026-110922, is a use-after-free vulnerability in the Prerender feature that could allow remote code execution. The company released Chrome 155.0.8059.85 and 155.0.8059.84 for Windows and macOS, along with Chrome 155.0.8059.84 for Linux on October 15. The critical issue was reported by an external researcher on October 2. Deployment will occur gradually over the next several days to weeks.