Filtered by vendor Gitea
Subscribe
Total
81 CVE
| CVE | Vendors | Products | Updated | CVSS v2 | CVSS v3 |
|---|---|---|---|---|---|
| CVE-2026-20897 | 1 Gitea | 1 Gitea | 2026-07-15 | N/A | 9.1 CRITICAL |
| 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. | |||||
| CVE-2026-20750 | 1 Gitea | 1 Gitea | 2026-07-15 | N/A | 9.1 CRITICAL |
| 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. | |||||
| CVE-2026-20736 | 1 Gitea | 1 Gitea | 2026-07-15 | N/A | 7.5 HIGH |
| 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. | |||||
| CVE-2026-20904 | 1 Gitea | 1 Gitea | 2026-06-17 | N/A | 6.5 MEDIUM |
| 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. | |||||
| CVE-2026-20888 | 1 Gitea | 1 Gitea | 2026-06-17 | N/A | 4.3 MEDIUM |
| 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. | |||||
| CVE-2026-20883 | 1 Gitea | 1 Gitea | 2026-06-17 | N/A | 6.5 MEDIUM |
| 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. | |||||
| CVE-2026-20800 | 1 Gitea | 1 Gitea | 2026-06-17 | N/A | 6.5 MEDIUM |
| 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. | |||||
| CVE-2026-0798 | 1 Gitea | 1 Gitea | 2026-06-17 | N/A | 3.5 LOW |
| 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. | |||||
| CVE-2023-3515 | 1 Gitea | 1 Gitea | 2026-06-17 | N/A | 4.4 MEDIUM |
| Open Redirect in GitHub repository go-gitea/gitea prior to 1.19.4. | |||||
| CVE-2022-46685 | 1 Gitea | 1 Gitea | 2026-06-17 | N/A | 4.3 MEDIUM |
| In Jenkins Gitea Plugin 1.4.4 and earlier, the implementation of Gitea personal access tokens did not support credentials masking, potentially exposing them through the build log. | |||||
| CVE-2022-42968 | 1 Gitea | 1 Gitea | 2026-06-17 | N/A | 9.8 CRITICAL |
| Gitea before 1.17.3 does not sanitize and escape refs in the git backend. Arguments to git commands are mishandled. | |||||
| CVE-2022-38795 | 1 Gitea | 1 Gitea | 2026-06-17 | N/A | 6.5 MEDIUM |
| In Gitea through 1.17.1, repo cloning can occur in the migration function. | |||||
| CVE-2022-38183 | 1 Gitea | 1 Gitea | 2026-06-17 | N/A | 6.5 MEDIUM |
| In Gitea before 1.16.9, it was possible for users to add existing issues to projects. Due to improper access controls, an attacker could assign any issue to any project in Gitea (there was no permission check for fetching the issue). As a result, the attacker would get access to private issue titles. | |||||
| CVE-2022-30781 | 1 Gitea | 1 Gitea | 2026-06-17 | 5.0 MEDIUM | 7.5 HIGH |
| Gitea before 1.16.7 does not escape git fetch remote. | |||||
| CVE-2022-27313 | 1 Gitea | 1 Gitea | 2026-06-17 | 5.0 MEDIUM | 7.5 HIGH |
| An arbitrary file deletion vulnerability in Gitea v1.16.3 allows attackers to cause a Denial of Service (DoS) via deleting the configuration file. | |||||
| CVE-2022-1928 | 1 Gitea | 1 Gitea | 2026-06-17 | 3.5 LOW | 5.4 MEDIUM |
| Cross-site Scripting (XSS) - Stored in GitHub repository go-gitea/gitea prior to 1.16.9. | |||||
| CVE-2022-1058 | 1 Gitea | 1 Gitea | 2026-06-17 | 5.8 MEDIUM | 6.1 MEDIUM |
| Open Redirect on login in GitHub repository go-gitea/gitea prior to 1.16.5. | |||||
| CVE-2022-0905 | 1 Gitea | 1 Gitea | 2026-06-17 | 5.5 MEDIUM | 7.1 HIGH |
| Missing Authorization in GitHub repository go-gitea/gitea prior to 1.16.4. | |||||
| CVE-2021-45331 | 1 Gitea | 1 Gitea | 2026-06-17 | 7.5 HIGH | 9.8 CRITICAL |
| An Authentication Bypass vulnerability exists in Gitea before 1.5.0, which could let a malicious user gain privileges. If captured, the TOTP code for the 2FA can be submitted correctly more than once. | |||||
| CVE-2021-45330 | 1 Gitea | 1 Gitea | 2026-06-17 | 7.5 HIGH | 9.8 CRITICAL |
| An issue exsits in Gitea through 1.15.7, which could let a malicious user gain privileges due to client side cookies not being deleted and the session remains valid on the server side for reuse. | |||||