| GO-2026-5091 | — | Gitea has insecure default SSH settings in code.gitea.io/gitea | 25/06/2026 |
| GHSA-3m6q-h5gj-7mrw | 보통 | Gitea has insecure default SSH settings | 22/04/2026 |
| CVE-2026-20912 | 심각9.1 | Gitea does not properly validate repository ownership when linking attachments to releases. An attachment uploaded to a private repository could potentially be linked to a release in a different public repository, making it accessible to unauthorized users. | 22/01/2026 |
| CVE-2026-20904 | 보통6.5 | Gitea does not properly validate ownership when toggling OpenID URI visibility. An authenticated user may be able to change the visibility settings of other users' OpenID identities. | 22/01/2026 |
| CVE-2026-20897 | 심각9.1 | Gitea does not properly validate repository ownership when deleting Git LFS locks. A user with write access to one repository may be able to delete LFS locks belonging to other repositories. | 22/01/2026 |
| CVE-2026-20888 | 보통4.3 | Gitea does not properly verify authorization when canceling scheduled auto-merges via the web interface. A user with read access to pull requests may be able to cancel auto-merges scheduled by other users. | 22/01/2026 |
| CVE-2026-20883 | 보통6.5 | Gitea's stopwatch API does not re-validate repository access permissions. After a user's access to a private repository is revoked, they may still view issue titles and repository names through previously started stopwatches. | 22/01/2026 |
| CVE-2026-20800 | 보통6.5 | Gitea's notification API does not re-validate repository access permissions when returning notification details. After a user's access to a private repository is revoked, they may still view issue and pull request titles through previously received notifications. | 22/01/2026 |
| CVE-2026-20750 | 심각9.1 | Gitea does not properly validate project ownership in organization project operations. A user with project write access in one organization may be able to modify projects belonging to a different organization. | 22/01/2026 |
| CVE-2026-20736 | 높음7.5 | Gitea does not properly verify repository context when deleting attachments. A user who previously uploaded an attachment to a repository may be able to delete it after losing access to that repository by making the request through a different repository they can access. | 22/01/2026 |
| CVE-2026-0798 | 낮음3.5 | Gitea may send release notification emails for private repositories to users whose access has been revoked. When a repository is changed from public to private, users who previously watched the repository may continue to receive release notifications, potentially disclosing release titles, tags, and content. | 22/01/2026 |
| CVE-2025-69413 | 보통5.3 | In Gitea before 1.25.2, /api/v1/user has different responses for failed authentication depending on whether a username exists. | 01/01/2026 |
| CVE-2025-68946 | 보통5.4 | In Gitea before 1.20.1, a forbidden URL scheme such as javascript: can be used for a link, aka XSS. | 26/12/2025 |
| CVE-2025-68945 | 보통5.3 | In Gitea before 1.21.2, an anonymous user can visit a private user's project. | 26/12/2025 |
| CVE-2025-68944 | 보통5.3 | Gitea before 1.22.2 sometimes mishandles the propagation of token scope for access control within one of its own package registries. | 26/12/2025 |
| CVE-2025-68943 | 보통5.3 | Gitea before 1.21.8 inadvertently discloses users' login times by allowing (for example) the lastlogintime explore/users sort order. | 26/12/2025 |
| CVE-2025-68942 | 보통5.4 | Gitea before 1.22.2 allows XSS because the search input box (for creating tags and branches) is v-html instead of v-text. | 26/12/2025 |
| CVE-2025-68941 | 보통5.3 | Gitea before 1.22.3 mishandles access to a private resource upon receiving an API token with scope limited to public resources. | 26/12/2025 |
| CVE-2025-68940 | 보통5.3 | In Gitea before 1.22.5, branch deletion permissions are not adequately enforced after merging a pull request. | 26/12/2025 |
| CVE-2025-68939 | 보통5.3 | Gitea before 1.23.0 allows attackers to add attachments with forbidden file extensions by editing an attachment name via an attachment API. | 26/12/2025 |