Gitea
Gitea API token scope escalation through HTTP signatures
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.
First public PoC
None yetno public PoC found
Public PoCs00 on GitHub
CVSS8.1high · scored by CISA ADP · CWE-266
CISA KEV
Not listednot known exploited
Affected versions and mitigation
From the CVE record and the vendor's references.Affected
Gitea Gitea
- <= 1.26.4
Mitigation
The record names no fix. Check the vendor advisory below.
References
- Vendor advisory github.com/go-gitea/gitea/security/advisories/…
- Release notes blog.gitea.com/release-of-1.27.2
- Patch github.com/go-gitea/gitea/pull/38862
2 more
Timeline
Days relative to CVE publicationNo public PoC found yet; not in CISA KEV.
PoC repositories
Found on GitHub.No PoC repositories found yet.