GO · JULY 2026 · EARLY WARNING

Gitea API Endpoint Vulnerability: Potential Privilege Escalation

EARLY WARNING · UNCONFIRMED. This page describes a developing threat that 0Day surfaced from early signals and has not yet independently confirmed. Details may change. Always verify against the primary sources before acting.
GHSA-683J-3FF6-HH2XSeverity: HIGH

An early warning has been issued regarding a potential vulnerability in Gitea's API endpoint for creating Personal Access Tokens, which may allow privilege escalation.

What happened

Reportedly, Gitea's API endpoint for creating Personal Access Tokens appears to allow privilege escalation via access token scope escalation. This means that an attacker with a restricted token may be able to create a fully-privileged token without knowing the account password. This issue is under investigation and has been tracked under the ID GHSA-683J-3FF6-HH2X. The vulnerability is said to affect versions of Gitea introduced from version 0 and has been fixed in version 1.27.0. It is recommended to upgrade to the latest version of Gitea and review access token permissions to prevent unauthorized scope escalation. For more detailed information, primary sources should be consulted.

How 0Day mitigates this

MATCHED TO YOUR ACTUAL DEPENDENCY GRAPH0Day matches every incoming threat signal against your GitHub organization’s full dependency graph, including transitive dependencies. If gitea is anywhere in your dependency tree, the engineers who own the affected repositories get a push alert the moment it is flagged — no manual audit to remember to run.

Read how this differs from waiting on a scanner to catch a known advisory, or see the exact, read-only access 0Day needs to do this for an organization.

Join the 0Day waitlist →

← Back to all threats