Lunny

**Name of the Vulnerable Software and Affected Versions** Gitea versions prior to 1.26.1 **Description** In the Git Smart HTTP path, the system fails to enforce repository-scoped access-token permissions when tokens are provided via Bearer authentication. While the `CheckRepoScopedToken()` function is designed to validate scopes, it returns early if the request is not using HTTP Basic authentication. Consequently, a Personal Access Token (PAT) or OAuth2 token sent as `Authorization: Bearer <token>` bypasses scope checks entirely. This allows a token with limited permissions (for example, only `read:notification`) to perform operations such as cloning or fetching private repositories without the `read:repository` scope, or pushing to repositories without the `write:repository` scope, provided the token owner has the necessary repository RBAC permissions. The issue affects the `CheckRepoScopedToken()` function and impacts Git Smart HTTP routes. **Recommendations** Update Gitea to version 1.26.1 or later.

**Name of the Vulnerable Software and Affected Versions** Gitea versions prior to 1.5.2 **Description** The issue is related to a Cross Site Request Forgery (CSRF) vulnerability in the Gitea Git repository management system interface. This vulnerability can be exploited by a remote attacker to perform a CSRF attack by sending specially crafted POST requests, potentially altering the state of the system. The vulnerability is particularly dangerous with state-altering POST requests. **Recommendations** For versions prior to 1.5.2, update to version 1.5.2 or later to resolve the issue. As a temporary workaround, consider restricting access to API routes to minimize the risk of exploitation. Avoid using state-altering POST requests in the affected API routes until the issue is resolved.