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
YApi Abandoned Since 2022: Fork Yapix Exposes Forgable Project Tokens and Critical Sandbox Flaws
YApi, a widely used open-source API documentation and mocking platform with 27.7k GitHub stars, has received no updates since its 1.12 release in November 2022. The project accumulated 1,629 open issues, including an unaddressed remote code execution report via mock scripts. Security researcher Perruer created the Yapix fork to address broken dependencies, Node.js 22 incompatibility with deprecated crypto.createCipher, and 244 known vulnerabilities in production dependencies. Analysis revealed that project tokens could be forged by any user because the default passsalt key was a hardcoded five-character string published on GitHub. The original implementation used vm2 and Node vm for script execution, both of which are unsafe, allowing arbitrary server-side code execution. Yapix migrates to isolated-vm with strict memory and time limits, replaces SHA-1 password hashing with scrypt, and blocks MongoDB operator injection in API parameters.
Researchers Bypass RP2350 Secure Debug Lock with Laser Fault Injection and Photon Emission Microscopy
Security researchers have demonstrated a hardware attack that restores Secure Debug access on the RP2350 microcontroller revision A4 despite permanent OTP fuses disabling it. Using photon emission microscopy they first located the exact physical bits of the DEBUGEN register, then applied precisely timed 980 nm laser pulses to flip two critical bits and re-enable the Mem-AP ports. The attack requires decapping the chip from the backside and laboratory equipment costing around $250,000, but succeeds in seconds once calibrated. It bypasses the CRIT1.DEBUG_DISABLE fuse, TrustZone restrictions, and glitch detectors by resetting the device before firmware can re-lock the OTP page. The technique was developed against the updated A4 silicon released after the first Raspberry Pi Hacking Challenge. The work highlights that even heavily hardened microcontrollers remain vulnerable to sophisticated physical attacks when an attacker has direct silicon access.
ServiceNow AI Platform Affected by Five Vulnerabilities Including Critical SQL Injection Flaws
ServiceNow disclosed five vulnerabilities in its AI Platform on September 24, 2026, through a security advisory. Two of the issues received CVSS v4.0 base scores of 9.3 and were rated Critical. CVE-2026-13016 allows unauthenticated remote attackers to perform SQL injection and manipulate database contents under specific conditions. CVE-2026-86860 stems from improper authorization checks that enable data exfiltration and privilege escalation without authentication. The flaws were identified via internal testing, coordinated disclosure, and the company's bug bounty program. ServiceNow urges customers to apply the provided updates immediately to mitigate the risks.
CISA Adds Adobe Commerce and WSO2 Vulnerabilities to Known Exploited Vulnerabilities Catalog
The US Cybersecurity and Infrastructure Security Agency has added two actively exploited vulnerabilities to its Known Exploited Vulnerabilities catalog. CVE-2026-71362 affects Adobe Commerce and Magento, enabling attackers to escalate privileges through an authorization bypass flaw. CVE-2026-5430 impacts multiple WSO2 API management products and allows JWT authentication bypass, leading to administrator account takeover and remote code execution via arbitrary file uploads. Adobe issued an advisory in August 2026 recommending patches within 30 days, while WSO2 warned about the issue in May 2026. CISA has set a September 27, 2026 deadline for federal agencies to apply updates and investigate potential compromises.