Hackers are now actively exploiting a critical Gitea vulnerability, CVE-2026-60004
Hackers are now actively exploiting a critical Gitea vulnerability, CVE-2026-60004, according to CISA and multiple security reports released on August 26, 2026.
The flaw allows remote code execution (RCE) on vulnerable self-hosted Gitea servers and has been added to CISA's Known Exploited Vulnerabilities (KEV) catalog.
What is the vulnerability?
- CVE-2026-60004 is a critical code injection/RCE flaw with a CVSS score of 9.8.
- It affects Gitea versions 1.17 through 1.27.0 and is fixed in Gitea 1.27.1.
- An attacker with repository write access can abuse the diffpatch API endpoint to install a malicious Git hook and execute shell commands as the Gitea service account.
- Because many Gitea environments allow open registration by default, a threat actor may be able to simply create an account, create a repository, and exploit the vulnerability without needing stolen credentials.
Security researchers reported a real-world compromise in which attackers exploited CVE-2026-60004 against a self-hosted Gitea instance and deployed a cryptocurrency-mining payload. The victim initially discovered the incident after their hosting provider reported abnormally high CPU usage.
The attack chain reportedly:
- Registered an account on the exposed Gitea server.
- Created a repository.
- Triggered the diffpatch vulnerability.
- Executed commands inside the Gitea container.
- Downloaded and launched a miner-like payload.
A successful compromise could expose:
- Source code repositories
- Gitea configuration files
- Database credentials
- OAuth tokens
- Application secrets
- CI/CD environment data
For organizations using Gitea internally, especially internet-facing instances, this represents a significant risk of lateral movement and credential theft.
Upgrade immediately to Gitea 1.27.1 or later.
Disable open registration until patching is complete.
Review:
- Newly created user accounts
- Recently created repositories
- Gitea audit logs
- High CPU usage alerts
- Unexpected Git hooks or scripts
If your server was exposed and vulnerable, assume credentials may have been accessed and rotate:
- Database passwords
- OAuth secrets
- API tokens
- Internal service credentials
I would classify this as a high-priority patch-and-hunt item for any self-hosted Gitea environment.

Comments
Post a Comment