High severity · published Oct 14, 2026
CVE-2026-73804
Gitea API token scope escalation through HTTP signatures
8.1
CVSS
0.5%
EPSS
No
On KEV
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.
CVSS vector
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:N
Attack vector
Network
Complexity
Low
Privileges
Low
User interaction
None
Confidentiality
High
Integrity
High
Availability
None
Scope
Unchanged
Exploitation
Is it being used?
Exploit prediction (EPSS)0.5% · higher than 41% of CVEs
Exploited in the wildNo evidence yet
CISA KEVNot listed
Ransomware campaign useNot known
Affected products
Which versions
GI
Gitea · Gitea
through 1.26.4 · source: vendor
Affected product
GI
Gitea
Gitea
More from Gitea
9.8
CVE-2026-60004
Gitea Code Injection Vulnerability
9.8
CVE-2026-59774
Gitea Org-mode file disclosure and code execution
9.8
CVE-2026-73278
Gitea WebAuthn bypass during OAuth and OIDC sign-in
9.8
CVE-2026-94205
Gitea fork workflow approval bypass through maintainer-triggered events
9.8
CVE-2022-42968
Gitea before 1.17.3 does not sanitize and escape refs in the git backend