ZDF
Sign inSign up

Vulnerabilities

Vulnerability · CVE-2026-73804

Gitea allows a token with write:user scope to register an attacker-controlled SSH public key on the token owner's account.

Published Oct 14, 2026 · catalog updated Oct 18, 2026 · Gitea allows a token

Check if you run it

No confirmed exploitation is on record for CVE-2026-73804. EPSS is 0.24%. Act only if a listed version of Gitea allows a token is installed.

Gaps on this record

  • The stored product name is a package slug. The name on this page is taken from the title (Gitea allows a token).
  • No version range is stored. A customer cannot check an installed version against this record.
  • No vendor fix or required action is stored. Compare the linked advisory before you change production.
Severity
High8.1
Known exploitation
Not in CISA/VulnCheck KEV
EPSS
0.24%
Remediation
Advisory link
Affected products
See sources for product scope

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.

No affected version ranges are stored yet. Use the vendor advisory before you decide this record does not apply.

How to fix CVE-2026-73804

What to do

Three questions, each answered from this record only. Confirm the vendor advisory before you patch.

Should you patch?

No confirmed exploitation is on record for CVE-2026-73804. EPSS is 0.24%. Act only if a listed version of Gitea allows a token is installed.

Which versions are affected?

Affected version ranges are not on this record. Compare the installed version with the linked vendor advisory before you change production.

What should an analyst verify?

CWE-266; CWE-863: Incorrect Authorization. EPSS 0.24%. There is no CISA KEV listing. No Exploit-DB or Metasploit reference is linked. Use the source links for the original advisory.

Code

The project this record applies to. Exploit listings stay in References.

Timeline

Detection, updates, and resolution for this record.

  1. Oct 14, 2026 · NIST NVD

    Detected

    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 wh

  2. Oct 14, 2026 · NIST NVD

    Updated

    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 wh

  3. Oct 18, 2026 · NIST NVD

    Updated

    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 wh

Sources

  • CVE.orgVulnerability recordCVE-2026-73804

    Official CVE identifier

    cve.org
  • FIRST EPSSExploitation probabilityCVE-2026-73804

    30-day exploitation probability 0.2%

    first.org
  • NIST NVDVulnerability recordCVE-2026-73804

    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

    nvd.nist.gov

References

Freshness

Last verified in this catalog Oct 18, 2026. Significant claims (KEV, EPSS, CVSS, affected ranges) come from the source rows above — open the original publisher for the authoritative advisory.