Over 8,300 Gitea Servers Remain Exposed to Remote Code Execution via CVE-2026-60004

Thousands of Gitea instances reachable from the internet remained unpatched at the end of August against CVE-2026-60004, a critical flaw that permits remote command execution. The fix arrived with Gitea 1.27.1, and the vulnerability has already been listed as actively exploited in the CISA KEV catalog.

The Gitea ecosystem, one of the most widely used platforms for hosting Git repositories in self-managed environments, faces a serious issue: as of August 27, 2026, 8,393 internet-exposed instances were still vulnerable to CVE-2026-60004, a critical remote code execution flaw. The situation is concerning because the vulnerability is not theoretical; active exploitation has been observed and the window for applying the patch has narrowed significantly.

The defect combines two elements that together allow an attacker to execute commands on the server. First, the diffpatch endpoint can be abused to inject content. Second, that content can lead to the installation and execution of a Git hook controlled from within the repository itself. The end result is a server running commands without the attacker needing prior operating-system access. Execution occurs without administrator privileges but with the permissions of the account running the service, typically the system user under which Gitea operates.

In many deployments this level of access is sufficient to enable data exfiltration of configuration secrets, database credentials, integration tokens, OAuth credentials, and sensitive environment variables. The actual impact depends on deployment isolation and permission models, especially when the instance runs on a shared host or with overly permissive rights.

Exploitation requires write access to a repository, yet a common weak point exists: open user registration is enabled by default in many installations. This allows an attacker to register, create a repository, and complete the attack chain without prior credentials, particularly when email confirmation is not required and anti-automation controls are absent.

The project addressed CVE-2026-60004 in Gitea 1.27.1, published on July 27, 2026. Nevertheless, the volume of unpatched instances indicates a broad attack surface, with heightened exposure for services that publish their forge directly on the internet. CISA added the flaw to the Known Exploited Vulnerabilities catalog on August 25 and set August 28 as the remediation deadline for U.S. federal agencies.

In some reported incidents, attackers used the access to deploy cryptocurrency-mining software on Docker-based installations. This pattern aligns with typical behavior against exposed services: rapid intrusion, immediate monetization, and minimal persistence. No public attribution to a specific actor or campaign has been confirmed.

Recommended actions include updating Gitea to at least version 1.27.1 and, where possible, prioritizing 1.27.2. Administrators should disable open registration if not essential or harden it with email confirmation and CAPTCHA. Indicators of compromise to review include anomalous creation or execution of Git hooks, unusual patterns on the diffpatch endpoint, sustained CPU usage, and unexpected binary downloads from the instance.

If intrusion is suspected, immediate steps include rotating all credentials and secrets, from configuration keys and database credentials to integration tokens and OAuth secrets. To reduce future exposure, network access should be restricted to necessary ranges and write permissions tightly controlled. In Docker deployments, container isolation, outbound connectivity restrictions, and network/permission hardening are advised, as command execution inside the container can escalate if the environment contains additional weaknesses.

Users of reverse-proxy authentication headers should also verify their configuration: the official Gitea Docker image is affected by a separate authentication bypass, CVE-2026-20896, when headers such as X-WEBAUTH-USER are enabled.