Gitea: Remote Code Execution via diffpatch Git Hook Installation (CVE-2026-60004)

What is affected, what to do

Gitea before 1.27.1 allows remote code execution via the diffpatch API through Git hook installation.

The vulnerability is being actively exploited; treat it as a priority. Update Gitea to version 1.27.1. Immediate actions, mitigation and detection rules are in the runbook below.

Affected

• Gitea lt 1.17..1.27.1

Fixed in

• Gitea 1.27.1

Not sure whether and how you are affected? Ask a question about this vulnerability

Metrics

Response and mitigation

1. 01

   Runbook step 1

   Immediate response (0-24 h)

   • Upgrade to Gitea 1.27.1. All releases from 1.17.0 up to (but not including) 1.27.1 are affected. For container deployments, pin the image to 1.27.1 rather than relying on latest. Confirm the running version with gitea --version or GET /api/v1/version.
   • Block the diffpatch endpoint at the reverse proxy until patched. Return 403 for POST /api/v1/repos/*/*/diffpatch. Legitimate use of this endpoint is rare, so blocking it costs little and closes the documented attack path.
   • Turn off open self-registration. In app.ini, set [service] DISABLE_REGISTRATION = true. The "repository write access" precondition is meaningless when anyone can sign up and create their own repo. That is why this flaw rates as unauthenticated.
   • Hunt for planted hooks. Inspect <REPO_ROOT>/*/*.git/hooks/ for anything Gitea did not create itself. The expected files are typically pre-receive, update, post-receive and proc-receive, plus the *.d/gitea subdirectories. Flag modified contents, recent mtimes or unknown scripts. Example: find /data/git/repositories -path '*/hooks/*' -type f -newermt '2026-08-01' -ls.
   • If compromise is suspected, isolate the host and rotate secrets. The service account can read every repository, the database credentials and the app.ini secrets (SECRET_KEY, INTERNAL_TOKEN, JWT_SECRET). It can also reach OAuth2 client secrets, deploy keys and Actions runner and CI tokens. Treat all of them as exposed.
   • Review recently created accounts and repositories. Look for throwaway accounts registered only to run the exploit.
2. 02

   Runbook step 2

   Mitigation layers

   • Network segmentation: Keep the web UI (default 3000/TCP, or 443 behind a proxy) and SSH (22 or 2222/TCP) off the internet. Allow access only through VPN or ZTNA. Restrict the Gitea host's egress to the destinations it actually needs (mirror sources, SMTP, webhook targets). This blunts reverse shells and exfiltration.
   • WAF/reverse proxy rule: For nginx, use location ~* ^/api/v1/repos/[^/]+/[^/]+/diffpatch { return 403; }. Optionally inspect patch bodies for hooks/ or ../ paths. A Suricata rule can combine http.method; content:"POST"; http.uri; content:"/diffpatch"; with http.request_body; content:"hooks/";.
   • Configuration hardening: Enforce [security] DISABLE_GIT_HOOKS = true so users cannot edit hooks through the UI. Do not assume this setting stops the diffpatch path; it does not replace the upgrade. Also set ENABLE_PUSH_CREATE_USER/ORG = false.
   • Endpoint hardening: Run Gitea as a dedicated unprivileged user with no sudo rights and no Docker socket access. Where your hook usage allows, mount repository volumes noexec (test this first). Under systemd, apply NoNewPrivileges=true and ProtectSystem=strict, and limit ReadWritePaths to the data directory.
   • IAM/least privilege: Cut repository write permissions back to the people who genuinely need them. Inventory personal access tokens with write:repository scope and revoke stale ones. Enforce 2FA for admins.
3. 03

   Runbook step 3

   Detection rules

   • Proxy/web access logs: Until you have patched, investigate every POST /api/v1/repos/*/*/diffpatch. SPL example: index=proxy uri_path="/api/v1/repos/*/diffpatch" http_method=POST | stats count by src_ip, user, uri_path. Escalate hits from freshly registered accounts.
   • EDR process ancestry (Sysmon EID 1 / Linux EDR): Treat gitea → git → sh/bash/dash → curl/wget/nc/python/perl as high severity. KQL example: DeviceProcessEvents | where InitiatingProcessParentFileName in~ ("gitea","git") and FileName in~ ("bash","sh","nc","curl","wget","python3") and ProcessCommandLine !has "gitea hook". Legitimate hooks invoke gitea hook --config=....
   • auditd/FIM: Add the watch -w /data/git/repositories -p wa -k gitea_hooks and filter on paths containing /hooks/. Sigma shape: logsource: linux/file_event, TargetFilename|contains: '.git/hooks/', Image|endswith: '/git', with an allowlist for Gitea's standard hook files.
   • Network telemetry (Zeek/Suricata): Watch for new outbound connections from the Gitea host to unfamiliar destinations, especially long-lived TCP sessions on unusual ports shortly after a diffpatch request. DNS lookups for paste or tunnelling services are also suspicious.
   • Gitea application log: Correlate /diffpatch entries in the router log with the requesting user. Repeated git apply or patch failures suggest exploit trial and error.

Detection rules

No NEOSEC detection rule is available for this vulnerability yet.

Classification under NIS2 and CRA

Rule-based classification from exploitation status and severity. It does not replace a case-by-case assessment.

NIS2

NIS2 is EU Directive (EU) 2022/2555 to raise the level of cybersecurity across the Union. It substantially broadens obligations compared with the first NIS directive: more sectors, mandatory risk management, staged reporting duties and personal accountability of senior management.

Read in glossary

Actively exploited: treat the vulnerability as a priority in vulnerability handling under Art. 21(2)(e) NIS2. If it is exploited in your environment, check the reporting obligation under Art. 23 (early warning within 24 hours).

CRA

The CRA is EU Regulation (EU) 2024/2847 setting horizontal cybersecurity requirements for „products with digital elements“ — from industrial controllers and software to connected consumer devices. For the first time manufacturers must ensure security across the entire product lifecycle, handle vulnerabilities and provide security updates.

Read in glossary

Since 11.09.2026, manufacturers of affected products with digital elements must report actively exploited vulnerabilities under Art. 14 CRA, with an early warning within 24 hours via ENISA's single reporting platform.

ISO/IEC 27001

ISO/IEC 27001 is the internationally leading standard for an information security management system (ISMS). It describes a risk-based, process-oriented framework to systematically plan, implement, review and improve information security.

Read in glossary

Control A.8.8, management of technical vulnerabilities: assess relevance to your systems, plan remediation and keep evidence.

Description

Gitea before 1.27.1 allows remote code execution via the diffpatch API through Git hook installation.

Source: BSI WID Portal, BSI CSAF, GitHub Security Advisories, cvelistv5, OSV (Open Source Vulnerabilities), CISA KEV Catalog, NVD (NIST), CVE.org (MITRE), pwn.watch

Vendors and products

• Gitea Gitea
• Go Code.gitea.io/gitea
• Go Gitea.dev
• Open Source Gitea

Weakness classes (CWE)

• CWE-94Improper Control of Generation of Code ('Code Injection')

  Base

  The product constructs all or part of a code segment using externally-influenced input from an upstream component, but it does not neutralize or incorrectly neutralizes special elements that could modify the syntax or behavior of the intended code segment.

  Entry at MITRE CWE-94

References & sources

• blog.gitea.comrelease-of-1.27.1
• github.comGitea Gitea — CVE-2026-60004pwn-watch
• runzero.comblog/gitea
• github.com0xBlackash/CVE-2026-60004
• NVD (NIST)NVD: CVE-2026-60004web, pwn-watch
• cisa.govknown-exploited-vulnerabilities-catalog?field_cve=CVE-2026-60004web, government-resource
• github.comgo-gitea/gitea/pull/38637web
• github.comgo-gitea/gitea/pull/38638web
• github.comgo-gitea/gitea/commit/470d34b1de87d901bd9135564d5ee18c0d339e82web
• github.comgo-gitea/gitea/commit/d7bc52beeadff4be5f5690de4d5de42abd10affeweb
• blog.gitea.comrelease-of-1.27.1web
• github.comgo-gitea/giteapackage
• github.comgo-gitea/gitea/releases/tag/v1.27.1web
• runzero.comblog/giteaweb
• pwn.watchpwn.watch: Gitea Gitea: Gitea Code Injection Vulnerabilitypwn-watch
• cisa.govCISA Known Exploited Vulnerabilities Catalogpwn-watch

Changes to this CVE

Who changed this CVE and when: NVD (analysis, affected products, CVSS), the CVE publisher (CNA) and additional providers such as CISA (ADP).

1. 26.08.2026CISA KEV entry updated9119a7d8…

   4 individual changes: Date Added, Due Date, Required Action, Vulnerability Name

   Show 4 original changes

   Individual changes of this event as published by NVD

   Type	Action	Before	After
   Date Added	added	—	2026-08-25
   Due Date	added	—	2026-08-25
   Required Action	added	—	2026-08-25
   Vulnerability Name	added	—	2026-08-25

   Source identifier: 9119a7d8-5eab-497f-8521-727c672e3725

2. 26.08.2026Record modifiedCISA ADP

   CISA assessment (SSVC): exploitation: active, automatable: yes

   New references:

   • https://www.cisa.gov/known-exploited-vulnerabilities-catalog?field_cve=CVE-2026-60004
   Show 2 original changes

   Individual changes of this event as published by NVD

   Type	Action	Before	After
   Reference	added	—	https://www.cisa.gov/known-exploited-vulnerabilities-catalog?field_cve=CVE-2026-60004
   SSVC assessment	added	—	{"id":"CVE-2026-60004","role":"CISA Coordinator","options":[{"exploitation":"active"},{"automatable":"yes"},{"technicalImpact":"total"}],"version":"2.0.3","timestamp":"2026-08-26T20:21:46.783249Z"}

   Source identifier: 134c704f-9b21-4f2e-91b3-4a467353bcc0

Linked advisories

• CISA Adds 10 CVEs to Known Exploited Vulnerabilities Catalog, Five with Three-day Mitigation DeadlinesSANS NewsBites28.08.2026
• @RISK®: The Consensus Security Vulnerability Alert: Vol. 26, Num. 33SANS @RISK27.08.2026
• Critical Gitea RCE Actively Exploited as Reported Attack Drops Miner-Like PayloadThe Hacker News26.08.2026
• CISA Warns of Exploited Gitea VulnerabilitySecurityWeek26.08.2026