CVE-2026-73804
Gitea allows a token with write:user scope to register an attacker-controlled SSH public key on the…
- Risk score
- 56/100
- CVSS
- 8.1 v3.1
- Exploit chance (30 days)
- 0.4%
- Published
- 14 Oct 2026
Open in the live forecast Today's forecast
What to know
- What it is
- Gitea allows a token with write:user scope to register an attacker-controlled SSH public key on the token owner's account. API requests signed with the corresponding private key authenticate as that account through HTTP Signature without API token scope information, causing route-level token scope checks to be skipped…
- Affected
- See advisory
- Fix
- Apply the vendor's security update; see the linked advisory.
- Exploitation
- No known exploitation
Why it is Yellow
- CVSS 8.1 high
References
- https://blog.gitea.com/release-of-1.27.2/
- https://github.com/go-gitea/gitea/pull/38862
- https://github.com/go-gitea/gitea/pull/38895
- https://github.com/go-gitea/gitea/releases/tag/v1.27.2
- https://github.com/go-gitea/gitea/security/advisories/GHSA-q55v-4cmj-xh65
- https://github.com/go-gitea/gitea/security/advisories/GHSA-q55v-4cmj-xh65
Original description
Gitea allows a token with write:user scope to register an attacker-controlled SSH public key on the token owner's account. API requests signed with the corresponding private key authenticate as that account through HTTP Signature without API token scope information, causing route-level token scope checks to be skipped. This converts a user-scoped token into an unscoped API authentication method while retaining the account's normal role and repository permissions.
Last activity 14 Oct 2026. Patch Forecast updates every hour.