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.
Fix
Nothing published yet: no patch, vendor advisory or mitigation reference on NVD, no vendor advisory in the News for this CVE, not in CISA's KEV, no fixed package version. BaselineWatch does not guess at one.
Change history 2
- CVSS8.1 (v3.1, CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:N)NVD modified 2026-10-18 14:16
- First seenunscoredNVD modified 2026-10-14 16:04
Affected (CPE criteria) 0
NVD has not attached CPE configurations yet.
References 6
- 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