CVE-2026-73804
Gitea API token scope escalation through HTTP signatures
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.
INFO
Published Date :
Oct. 14, 2026, 3:17 p.m.
Last Modified :
Oct. 14, 2026, 3:17 p.m.
Remotely Exploit :
No
Source :
88ee5874-cf24-4952-aea0-31affedb7ff2
Solution
- Validate token scope for user SSH key registration.
- Validate token scope during HTTP Signature authentication.
- Enforce API token scope checks on authenticated requests.
- Update Gitea to the latest secure version.
References to Advisories, Solutions, and Tools
Here, you will find a curated list of external links that provide in-depth
information, practical solutions, and valuable tools related to
CVE-2026-73804.
CWE - Common Weakness Enumeration
While CVE identifies
specific instances of vulnerabilities, CWE categorizes the common flaws or
weaknesses that can lead to vulnerabilities. CVE-2026-73804 is
associated with the following CWEs:
Common Attack Pattern Enumeration and Classification (CAPEC)
Common Attack Pattern Enumeration and Classification
(CAPEC)
stores attack patterns, which are descriptions of the common attributes and
approaches employed by adversaries to exploit the CVE-2026-73804
weaknesses.
We scan GitHub repositories to detect new proof-of-concept exploits. Following list is a collection of public exploits and proof-of-concepts, which have been published on GitHub (sorted by the most recently updated).
Results are limited to the first 15 repositories due to potential performance issues.
The following list is the news that have been mention
CVE-2026-73804 vulnerability anywhere in the article.
The following table lists the changes that have been made to the
CVE-2026-73804 vulnerability over time.
Vulnerability history details can be useful for understanding the evolution of a vulnerability, and for identifying the most recent changes that may impact the vulnerability's severity, exploitability, or other characteristics.
-
New CVE Received by 88ee5874-cf24-4952-aea0-31affedb7ff2
Oct. 14, 2026
Action Type Old Value New Value Added 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. Added CWE CWE-266 Added CWE CWE-863 Added Affected New affected value received. <a href="https://github.com/CVEProject/cvelistV5/blob/main/cves/2026/73xxx/CVE-2026-73804.json">CVE-2026-73804</a> Added Reference https://blog.gitea.com/release-of-1.27.2/ Added Reference https://github.com/go-gitea/gitea/pull/38862 Added Reference https://github.com/go-gitea/gitea/pull/38895 Added Reference https://github.com/go-gitea/gitea/releases/tag/v1.27.2 Added Reference https://github.com/go-gitea/gitea/security/advisories/GHSA-q55v-4cmj-xh65