# Gitea: Remote Code Execution via diffpatch Git Hook Installation Advisory record · `GHSA-rcr6-4jqh-j84m` - **Identifiers:** `GHSA-rcr6-4jqh-j84m` · `BIT-gitea-2026-60004` · `CVE-2026-60004` · `GO-2026-6433` - **State:** Confirmed - **Severity:** CVSS 9.8 Critical - **Critical:** Yes: KEV, CVSS 9+, CVSS 7+ and EPSS - **Weakness (CWE):** [CWE-94](https://cwe.mitre.org/data/definitions/94.html) - **Tags:** [Code injection](https://agentprime.io/advisories/tag/code-injection.md) - **Published:** 8 Sept 2026 - **Updated:** 10 Sept 2026 - **Reviewed by a person:** No Published by the GitHub Advisory Database at 8 Sept 2026, 17:56 UTC. agentprime has not analysed this yet, so whether it affects any app is not known. ## Critical Critical, because: - In CISA’s KEV catalogue since 25 Aug 2026: it is known to be exploited. - CVSS score 9.8: 9.0 or more. - CVSS score 9.8 (7.0 or more) and EPSS 0.24 (0.1 or more): a high score and a real chance of exploitation in the next 30 days. How we decide what’s critical: ## Affected packages - `gitea.dev` (Go): affected `>=1.17.0, <1.27.1`; fixed in `1.27.1` ## Machine-written summary Summary written by Claude Haiku from the source advisory. Not reviewed by a person. > Gitea versions from 1.17.0 before 1.27.1 are vulnerable to remote code execution through the diffpatch endpoint. An attacker with write access to a repository can run arbitrary shell commands as the Gitea OS user, and if open registration is enabled, an unauthenticated visitor can register an account, create a repository, and do this. Upgrade to Gitea 1.27.1 or later. The source gives few details on workarounds. Written 1 Nov 2026. ## Not analysed yet We haven’t published our analysis of this Advisory yet. Once a person has reviewed it, this page will say what’s vulnerable, what has to be true for your app to be affected, and how to check. ## Severity and exploitation - 9.8 Critical, CVSS 3.1: `CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H`, from CNA (mitre) - **CISA KEV:** Listed since 25 Aug 2026: known to be exploited. - **EPSS:** 0.24, the 97th percentile, on 12 Nov 2026: FIRST’s estimate of the chance of exploitation in the next 30 days. ## Timeline - 31 Oct 2026, 14:13 UTC: First seen by agentprime - 31 Oct 2026, 14:13 UTC: [Confirmed by OSV](https://osv.dev/vulnerability/GHSA-rcr6-4jqh-j84m) ## Sources - [GitHub Advisory Database: GHSA-rcr6-4jqh-j84m](https://github.com/advisories/GHSA-rcr6-4jqh-j84m) - [OSV: GHSA-rcr6-4jqh-j84m](https://osv.dev/vulnerability/GHSA-rcr6-4jqh-j84m) - - - - - - - - - - - - Facts on this page come from the GitHub Advisory Database (CC-BY 4.0), OSV and the other sources listed, as published. We don’t reproduce full advisory descriptions, which can contain exploit code. ## Check whether this affects you A Match means an installed version is in the affected range above. Most don’t affect the app; agentprime hasn’t analysed this one yet. - With the agentprime MCP server (), ask your agent to check the project: `check_lockfile` sends a lockfile, `check_packages` a list of installed packages, and both return the Matches and the upgrades that clear them. `get_advisory` returns this record. Setup: - In a browser: reads your lockfile in the browser, never uploading it. - Whether it touches your code, with file and line: the Claude Code plugin, - As JSON: , or `POST https://api.agentprime.io/v1/match` with your packages () --- The web page: . Everything for agents: .