Details
Until a patched release lands, operators can mitigate by either:
- Removing the
Repository.Release.AllowedTypesallowlist (accept any extension) -- this eliminates the bypass but also removes the defense, so it is only a holding move. - Putting Gitea behind a reverse proxy that rewrites or strips suspicious
attachment-edit-*form fields on POST to/<owner>/<repo>/releases/edit/*-- viable but operationally fragile. - Restricting who has Write permission on repositories with a configured release allowlist -- in single-tenant deployments this may be acceptable.
A vendor patch is the right answer; the workarounds above are stopgaps.
Credit
Jose Rivas (bl4cksku111.com)
References
- Parent advisory: https://github.com/advisories/GHSA-263q-5cv3-xq9g (CVE-2025-68939)
- Parent fix: PR https://github.com/go-gitea/gitea/pull/32151 (commit
7adc4717ec) - CWE-424: https://cwe.mitre.org/data/definitions/424.html
- CWE-434: https://cwe.mitre.org/data/definitions/434.html