Hispasec•August 31, 2026•🇪🇸Translated from Spanish

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.

Related articles

Security NEXT•Vulnerabilities & Exploits

Critical PHP Vulnerability to Receive Patch on November 19 at 23:00 JST

A critical-severity vulnerability has been identified in the PHP scripting language, affecting all supported branches. The PHP security team has pre-announced a security update release scheduled for 14:00-14:30 UTC on November 19, which corresponds to 23:00-23:30 Japan Standard Time. Although the maximum severity rating is critical, the flaw does not impact default configurations and requires uncommon system setups to be exploitable. No specific technical details, CVE identifiers, or attack vectors have been disclosed ahead of the patch. The update forms part of PHP's regular four-week release cycle. This follows another serious PHP flaw called PHP2Shell that required emergency remediation in October. Organizations are strongly advised to prepare for immediate deployment once the fix becomes available.

BoletimSec•Vulnerabilities & Exploits

Java4Shell Vulnerability Enables Remote Code Execution Without Authentication Across Keycloak, Jira, Confluence and Other Enterprise Platforms

A critical flaw tracked as CVE-2026-114938 and dubbed Java4Shell allows unauthenticated remote code execution on multiple widely deployed Java applications including Keycloak, Jira, Confluence, JFrog Artifactory, Jenkins and PingFederate when running in their default configurations. The root cause lies in a buffer overflow inside the AVX-512-accelerated Base64 decoder of HotSpot JVM on x86-64 processors that support the VBMI instruction set. Malformed Base64 strings ending with an extra equals sign cause the decoder to write 62 or 63 bytes past the allocated output buffer before the Java runtime rejects the input. Because several authentication-related components such as Basic Auth headers, SAML artifacts and CSRF tokens are decoded before any session or access-control checks occur, the vulnerable code path executes with attacker-controlled data prior to authentication. The issue affects Java 17.0.6 and later releases on lines 21, 25 and 27 when running on Intel Xeon Ice Lake or newer and AMD Zen 4 CPUs; ARM64 systems remain unaffected. Oracle and OpenJDK released fixes on 18 November, CISA issued an urgent advisory the same day, and Amazon has already updated Corretto builds while Red Hat continues work on its distributions.

BoletimSec•Vulnerabilities & Exploits

Attackers Exploit Critical Apache Roller Flaw CVE-2026-129448 for Unauthenticated Remote Code Execution

Cybercriminals are actively exploiting a critical vulnerability in Apache Roller that allows remote code execution on the server without any credentials. The Java-based blogging platform received CVE-2026-129448 with a CVSS score of 9.8, and the Apache Software Foundation has confirmed active exploitation in the wild. The attack path targets the XML-RPC endpoint, which accepts vendor extension types and deserializes requests before performing authentication. The flaw affects versions 4.0.0 through 6.1.4, expanding the scope beyond the earlier CVE-2026-82384 that only listed version 6.1.5 as affected. Disabling XML-RPC through the admin interface provides no protection on older versions because deserialization occurs before the setting is checked. The recommended fix is upgrading to version 6.1.6 or later, which properly disables extension types and enforces the configuration. Organizations unable to update immediately should set enabledForExtensions to false in web.xml or remove the XML-RPC servlet mapping.

Habr•Vulnerabilities & Exploits

PHP Prepares Critical Patches for All Supported Versions One Month After Emergency Update

The PHP development team announced on November 18 that it will release updates for all supported interpreter versions to address multiple vulnerabilities, including critical ones. The fixes target a use-after-free flaw in file upload progress tracking that can lead to remote code execution when specific session serialization formats are combined. This comes shortly after emergency patches issued on October 21 resolved two remote code execution issues collectively known as PHP2Shell. The new vulnerability, tracked as CVE-2026-115560 with a CVSS score of 9.8, arises when applications switch session formats from php_binary or php_serialize to php after upload tracking has begun. Developers are advised to disable session.upload_progress.enabled until patches are applied and verified. Releases are scheduled for November 19 between 17:00 and 17:30 Moscow time, accompanied by a detailed security bulletin.