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
Ghost Assets in Vulnerability Management: How Identification, Merging and Asset History Eliminate Anomalies in MaxPatrol VM
Positive Technologies experts explain how infrastructure changes create duplicate, merged and phantom assets that distort vulnerability management. The article details three core mechanisms inside MaxPatrol VM: unique asset identification across scan sources, non-destructive merging of new and existing data, and full lifecycle history with configurable aging policies. It describes how the system distinguishes assets using prioritized keys such as system ID, FQDN, MAC address and VM ID, then applies recursive merging rules that respect multiple data sources. Policies allow teams to set freshness and obsolescence thresholds, automatically hiding assets after 90 days while preserving historical snapshots for PDQL queries. The piece also covers practical cloning and partial-scan scenarios that can produce misleading duplicates or lingering collections.
GreyNoise Detects Active Exploitation Attempts of CVE-2021-36260 Against Hikvision Cameras
GreyNoise recorded exploitation attempts targeting CVE-2021-36260 in Hikvision cameras and recorders between September 21 and October 1. The vulnerability carries a CVSS score of 9.8 and allows unauthenticated remote command execution through insufficient input validation in the embedded web server. Attack traffic originated from four IP addresses, three routed through a commercial VPN in Lithuania and one from a Ukrainian residential network, with all targets located in Ukraine. Attackers leveraged a publicly available Nuclei template to probe devices, though GreyNoise confirmed only scanning activity and not successful compromises. The five-year-old flaw remains actively scanned despite an available firmware patch from Hikvision and a CISA advisory recommending immediate updates. Password changes provide no protection because the attack requires no authentication. Defenders are advised to apply firmware updates, remove devices from public internet exposure, and segment video surveillance networks from critical infrastructure.
Splunk Enterprise Discloses 46 Vulnerabilities Including Critical Patroni Authentication Flaw
Splunk has published three security advisories detailing a total of 46 vulnerabilities affecting Splunk Enterprise and related components. Three of the issues were rated critical, with CVE-2026-76268 receiving a CVSS v3.1 base score of 9.8. The flaw resides in the Patroni REST API used for PostgreSQL cluster management within search head clusters, allowing unauthenticated remote attackers to execute arbitrary operating system commands. Another high-severity issue, CVE-2026-76266, enables local privilege escalation to root on Linux systems during package updates. The remaining vulnerabilities cover product code, internally identified problems, and third-party packages. Organizations are urged to apply the available patches promptly.
Smart Fish Tank Power Strip Server Breached, Killing Aquarium Fish During National Day Holiday
During China's National Day holiday, the cloud servers of Woda Technology's smart power strips for fish tanks were compromised by malicious hackers, causing widespread remote disconnections and power outages for user devices. The attack left heating rods, oxygen pumps, and circulation systems offline for hours, resulting in the deaths of koi, arowana, and other ornamental fish that users had maintained for years. Woda issued a public notice confirming the intrusion was not a product defect or user error but a deliberate network attack, and the company has since upgraded firewalls, added multi-layer cloud protections, deployed backup servers, and improved local offline logic to prevent future failures. The incident highlights a critical IoT design flaw where devices rely entirely on vendor cloud platforms for control, allowing attackers who breach the server to remotely manage household appliances at scale. Security experts note that the same architecture is used across smart speakers, locks, cameras, and other consumer devices, creating a broad attack surface with minimal updates or segmentation. Woda has reported the case to authorities and preserved logs for forensic investigation.