Threat database

Gitea versions before 1.25.5 allow draft release data or attachments to be accessed without the required write permission.

Gitea versions before 1.25.5 allow a user to change another user's primary email address.

Gitea versions before 1.25.5 do not enforce a timeout on git grep searches, allowing expensive searches to consume server resources.

Gitea versions before 1.25.5 do not use the migration HTTP transport for LFS push and sync mirror operations, bypassing the configured migration transport protections for those LFS requests.

Gitea versions before 1.25.5 do not persist the OAuth2 PKCE S256 challenge method correctly during authorization, allowing token exchange without the expected verifier check.

Gitea versions before 1.25.5 do not consistently enforce OAuth2 authorization code expiry and single-use behavior during token exchange.

Gitea versions up to and including 1.26.1 allow the Allow edits from maintainers permission path to authorize commits to repositories that the user can read but should not be able to write.

Gitea versions before 1.25.5 look up tracked-time entries by time ID without scoping the lookup to the issue in the request URL, allowing deletion attempts to target entries from another issue.

Gitea versions up to and including 1.25.4 allow redirect bypasses through raw or percent-encoded backslashes in redirect_to values.

Gitea versions before 1.25.5 mishandle path resolution during template repository generation, allowing template processing to read or write through symlinked or otherwise non-regular paths.

Gitea versions up to and including 1.26.1 do not apply public-only token filtering consistently to the user organization API, leaving an incomplete fix for CVE-2025-68941.

Gitea versions before 1.25.5 have insufficient visibility checks in organization permission APIs for hidden members and private organizations.

Gitea version 1.26.2 contains a vulnerability that allows unauthorized users to access labels of private organizations. This issue is classified under information exposure (CWE-200) and improper access control (CWE-862). The vulnerability has a high severity with a CVSS score of 7.5, indicating significant confidentiality impact without affecting integrity or availability. No official patch or remediation guidance is currently provided by the vendor.

Gitea versions before 1.25.5 have insufficient permission checks for updating or rebasing pull request branches.

Gitea version 1.26.2 contains a vulnerability where fork synchronization continues even after the parent repository's visibility changes from public to private. This behavior exposes data in the fork repository that should no longer be accessible, leading to unauthorized information disclosure.

Gitea Open Source Git Server versions up to and including 1.26.2 contain an incomplete Server-Side Request Forgery (SSRF) protection vulnerability in webhook and migration allow-list filtering. This vulnerability is identified as CWE-918 and has a critical severity rating with a CVSS score of 9.6. The flaw allows an attacker with limited privileges to potentially cause high confidentiality and integrity impact without user interaction. No official patch or remediation guidance is currently provided by the vendor.

Gitea versions before 1.26.0 allow API users to fork a repository into an organization without first passing the CanCreateOrgRepo check, which can expose organization secrets.

Gitea versions before 1.25.5 lack validation constraints for repository creation fields, including length-limited template fields and trust model or object format values.

Gitea versions before 1.25.5 have insufficient permission checks when listing tracked time entries.

Gitea Docker image versions up to and including 1.26.2 have a default configuration that trusts all source IPs for reverse-proxy authentication headers. This allows any source IP to impersonate a user when headers like X-WEBAUTH-USER are enabled, leading to a critical security vulnerability.