CVE-2026-73804 Gitea CVE debrief

Who should care

Gitea instance administrators and users with write:user scoped tokens should assess exposure and prioritize remediation. This includes reviewing Gitea instance configurations, verifying the presence of affected versions, and ensuring that remediation efforts are in place to prevent exploitation.

Why it matters

CVE-2026-73804 allows an attacker to escalate privileges through Gitea API token scope escalation, impacting Gitea instance administrators and users with write:user scoped tokens.

• Elevation of privileges through token scope escalation
• Potential unauthorized access to sensitive repositories
• Need for verification of Gitea instance exposure
• Priority for remediation through version updates or compensating controls

Technical summary

The vulnerability allows an attacker to register an attacker-controlled SSH public key on the token owner's account, effectively converting a user-scoped token into an unscoped API authentication method while retaining the account's normal role and repository permissions. This is caused by the lack of proper validation of HTTP signatures, allowing an attacker to bypass API token scope checks. The vulnerability impacts Gitea instance administrators and users with write:user scoped tokens, as it could lead to unauthorized access to sensitive repositories and elevation of privileges.

Defensive priority

Defenders should prioritize verifying Gitea instances for exposure, especially those with write:user scoped tokens, and ensure remediation through version updates or compensating controls.

Recommended defensive actions

• Verify Gitea instances for exposure, especially those with write:user scoped tokens
• Ensure remediation through version updates or compensating controls
• Monitor for suspicious activity related to API token usage
• Review compensating controls for exposed systems while remediation is scheduled and verified
• Check relevant monitoring, detection, and logs for exposed assets that need extra review
• Track exceptions, retest remediated assets, and close the item only after evidence is documented
• Confirm whether affected product deployments exist in managed environments and assign an owner for follow-up

Evidence notes

The CVE record and source item provide details on the vulnerability, including its description and affected versions. However, CVSS score and severity are not provided. The vulnerability is confirmed to exist in Gitea versions prior to 1.27.2. Official vendor advisories and release notes for Gitea version 1.27.2 provide additional context and guidance on remediation.

Sources and references

Methodology and review provenance

AI-assisted synthesis based on stored public vulnerability evidence. System validation, approval state, and publication status do not by themselves establish human review of this revision. PatchSiren helps prioritize defensive review and does not prove exposure or remediation on any system.