Vulnerability · Published Nov 1, 2026 · Assigned by Gitea
CVE-2026-116474Gitea Actions job token spoofing of instance-signed commits
Unrated
In plain English
A security flaw in Gitea from Gitea. There are no confirmed reports of exploitation so far. The chance it is exploited in the next 30 days is estimated at 0.1% (higher than 1% of all known vulnerabilities).
Official description
The `GITEA_TOKEN` of a Gitea Actions job authenticates as the `gitea-actions` system user, and the `/api/v1/user` email and GPG key endpoints accepted that user, so a job could register an email address and a GPG key on it; without required email confirmation (the default) the address is stored as activated. Commit verification treats a key without a real owner as the instance signing key, so any user who can run a workflow job could make commits signed with their own key show as trusted and signed by the instance in every repository where they appear, including pull requests to repositories the user cannot write to. The impact is limited to the displayed signature status: enforcement such as required signed commits only checks that a signature is verified and is unaffected, and no access is gained. The `/api/v1/user` routes now reject system users.
Affected products (as reported)
Weakness: CWE-347
References
- GitHub Security Advisory GHSA-mf6p-vqpw-3r7x vendor-advisory
- Fix: go-gitea/gitea pull request #39945 patch
- Fix backport to release/v28: go-gitea/gitea pull request #40115 patch
- Gitea 28.3.0 release announcement release-notes
- go-gitea/gitea v28.3.0 release release-notes