GPU VulnDB

Database/Control plane, storage & DevOps

Gitea: unauthenticated remote code execution via the diffpatch API installing Git hooks

CVE-2026-60004Control plane, storage & DevOpsKnown exploitedcurated

Impact

A self-hosted Gitea instance is usually where a GPU shop keeps training code, Dockerfiles, GitOps manifests and CI runner credentials. This flaw lets an unauthenticated caller reach the diffpatch API and install a Git hook, which the server then executes - so the attacker gets code execution as the Gitea service account on the git host. From there the practical damage is supply chain: poisoned image builds and manifests flow to the cluster on the next sync, and any deploy keys or CI tokens stored on that host are exposed. CISA lists it as exploited in the wild.

Who can reach it

Anyone able to reach the Gitea HTTP endpoint. No authentication required (CVSS PR:N), so an instance published to tenants or to the internet is directly exposed.

What to do

Upgrade to Gitea 1.27.1 as described in the release notes and GHSA-rcr6-4jqh-j84m, then restart the Gitea service - a single-daemon restart, no node drain and no cluster impact. Because exploitation leaves persistence behind, also inspect existing repositories for unexpected server-side hooks and rotate deploy keys, CI tokens and webhook secrets held by the instance.

References

Related entries

All Control plane, storage & DevOps entries

This entry is curated: imported from vendor advisories with machine assistance, not yet individually verified. Confirm against your vendor's advisory before acting, and report anything wrong.