CVE-2026-60004
CVE-2026-60004 is a security flaw in Gitea. Attackers can run their own code on Gitea. The US Cybersecurity and Infrastructure Security Agency (CISA) added it to its catalog of flaws known to be used in attacks on 25 Aug 2026.[1]
Gitea is business software or equipment. Most families won’t have it, but attackers break into it to get inside companies, and from there to what those companies hold about their customers, patients and staff. Fixed in version 1.27.1 of Gitea.
Description
CISA calls it a code injection in Gitea Gitea. In its words: “Gitea contains a code injection vulnerability that allows an attacker with repository write access to send a malicious patch to the diffpatch API endpoint to plant an executable Git hook and run shell commands as the Gitea service account.”[1]
The underlying weakness is code injection (CWE-94), in MITRE’s list of common software weaknesses.[2]
It scores 9.8 out of 10 on the Common Vulnerability Scoring System, which rates it critical, scored by the organisation that published the CVE using CVSS 3.1.[2]
Affected versions
NVD’s record lists one fixed version: everything before it is affected.[2]
| Product | Fixed in |
|---|---|
| Gitea | 1.27.1 |
Most families won’t have Gitea; it’s for whoever looks after IT at work.
Exploitation
CISA added it to its catalog of known exploited vulnerabilities on 25 Aug 2026. CISA lists a flaw only when it has reliable evidence of it being exploited, and gave US federal agencies until 28 Aug 2026 to fix it.[1]
FIRST’s Exploit Prediction Scoring System, which estimates how likely a flaw is to be used in attacks in the next 30 days from what it sees across the internet, puts it at 24%. That’s in the top 3% of the flaws it scores.[4]
CISA assesses it as automatable: attackers can run it against many targets at once.
CISA doesn’t say who was attacked, or how.
Fix
Gitea has published a fix or advice.[3] CISA’s required action: “Apply mitigations in accordance with vendor instructions, ensuring compliance with CISA’s BOD 26-04 Prioritizing Security Updates Based on Risk (see URL in Notes) guidance and CISA’s “Forensics Triage Requirements” (see URL in Notes).”[1]
- Check whether you use it.Gitea is business software or equipment, so most families won’t have it. If you run a business, or work from home on company equipment, ask whoever looks after your IT.
- Send this page to your IT person.Ask them to confirm it’s fixed (fixed in version 1.27.1 of Gitea), or not in use. CISA gave US government agencies until 28 Aug 2026 to fix it.
- If it can’t be fixed, take it offline.CISA’s advice when there’s no fix is to stop using the product, or take it off the internet, until there is one.
You can’t fix someone else’s server, but you can watch for what follows a break-in like this: a breach notice, a password reset you didn’t ask for, or a scam message that knows things it shouldn’t. HARD watches for those for you and your family.
Timeline
| Date | Event |
|---|---|
| CISA adds it to its catalog of flaws known to be used in attacks.[1] | |
| The flaw is made public in the National Vulnerability Database, with a severity score of 9.8.[2] | |
| CISA’s deadline for US government agencies to fix it.[1] | |
| FIRST puts the odds of it being used in attacks in the next 30 days at 24%.[4] |
See also
Other code injection flaws
- CVE-2026-0322, Palo Alto Networks PAN-OS: code injection ·
- CVE-2026-65660, Microsoft SharePoint: code injection ·
- CVE-2026-72530, TrueConf Server: code injection ·
- CVE-2025-62593, Ray-Project Ray: code injection ·
- CVE-2026-9198, IBM Langflow: code injection ·
References
- ^ Cybersecurity and Infrastructure Security Agency. “Gitea Code Injection Vulnerability”. Known Exploited Vulnerabilities Catalog, added 25 Aug 2026.
- ^ National Institute of Standards and Technology. “CVE-2026-60004 Detail”. National Vulnerability Database, published 26 Aug 2026.
- ^ Gitea. Advisories and fixes: github.com, blog.gitea.com.
- ^ FIRST. “Exploit Prediction Scoring System”. EPSS 0.240, percentile 97.8, 31 Oct 2026.
- CVE Program. “CVE-2026-60004”. The official CVE record.
This article is built from CISA’s catalog (version 2026.10.30), NVD’s record and FIRST’s scores, kept in HARD’s database and checked every morning. The plain English is HARD’s.