CVE-2026-60004 is a critical remote code execution vulnerability in Gitea affecting versions 1.17 through 1.27.0. The flaw is in the repository diffpatch functionality, where Gitea applies attacker-supplied patches inside a temporary bare clone using Git operations that include index-related options and, on Git 2.32 or later, a three-way merge fallback. By submitting a crafted patch that writes an executable file into the hook directory of the bare temporary repository and then triggering Git’s fallback behavior, an attacker with repository write access can cause a malicious Git hook to become active and execute during index updates. Because the commands run in the context of the Gitea service process, successful exploitation results in arbitrary shell command execution on the server. The issue was fixed in Gitea 1.27.1 by changing the temporary clone handling from bare to non-bare.
Mallory correlates every CVE against your assets, your vendors, and active adversary campaigns. Know which vulnerabilities matter for you, not just which ones are loud.
What it means. What to do now. Patch path, mitigations, and the assume-compromise checklist.
What an attacker gets, and what they’ve been doing with it.
If you can’t patch tonight, do this now.
Patch, then assume compromise.
No public exploits tracked yet. Mallory keeps watching.
No public exploit code observed for this vulnerability.
9 sources tracked across advisories, community write-ups, and news. New activity surfaces here as Mallory finds it.
A critical remote code execution vulnerability in Gitea’s diffpatch endpoint that allows an attacker with repository write access to place and trigger a malicious Git hook, resulting in arbitrary shell command execution as the Gitea service account.
A critical remote code execution vulnerability in Gitea that allows a user with ordinary repository write access to turn attacker-controlled patch content into a live Git hook and execute shell commands as the Gitea service account.
Query your assets running an affected version, and investigate the blast radius.
Every observed campaign linking this CVE to a named adversary.
Malware families riding this exploit, with evidence and IOCs.
YARA, Sigma, Snort, and vendor rules, auto-deployed to your SIEM.
Cross-references every affected SKU, including bundled OEM variants.
Community discussion across Reddit, Mastodon, and other social sources.