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.
References
Configurations
No configuration.
History
18 Oct 2026, 14:16
| Type | Values Removed | Values Added |
|---|---|---|
| References | () https://github.com/go-gitea/gitea/security/advisories/GHSA-q55v-4cmj-xh65 - | |
| CVSS |
v2 : v3 : |
v2 : unknown
v3 : 8.1 |
14 Oct 2026, 15:17
| Type | Values Removed | Values Added |
|---|---|---|
| New CVE |
Information
Published : 2026-10-14 15:17
Updated : 2026-10-18 14:16
NVD link : CVE-2026-73804
Mitre link : CVE-2026-73804
CVE.ORG link : CVE-2026-73804
JSON object : View
Products Affected
No product.
