Filtered by vendor Gitea
Subscriptions
Total
43 CVE
| CVE | Vendors | Products | Updated | CVSS v3.1 |
|---|---|---|---|---|
| CVE-2025-68941 | 1 Gitea | 1 Gitea | 2025-12-26 | 4.9 Medium |
| Gitea before 1.22.3 mishandles access to a private resource upon receiving an API token with scope limited to public resources. | ||||
| CVE-2025-68942 | 1 Gitea | 1 Gitea | 2025-12-26 | 5.4 Medium |
| Gitea before 1.22.2 allows XSS because the search input box (for creating tags and branches) is v-html instead of v-text. | ||||
| CVE-2025-68943 | 1 Gitea | 1 Gitea | 2025-12-26 | 5.3 Medium |
| Gitea before 1.21.8 inadvertently discloses users' login times by allowing (for example) the lastlogintime explore/users sort order. | ||||
| CVE-2025-68944 | 1 Gitea | 1 Gitea | 2025-12-26 | 5 Medium |
| Gitea before 1.22.2 sometimes mishandles the propagation of token scope for access control within one of its own package registries. | ||||
| CVE-2025-68946 | 1 Gitea | 1 Gitea | 2025-12-26 | 5.4 Medium |
| In Gitea before 1.20.1, a forbidden URL scheme such as javascript: can be used for a link, aka XSS. | ||||
| CVE-2025-68945 | 1 Gitea | 1 Gitea | 2025-12-26 | 5.8 Medium |
| In Gitea before 1.21.2, an anonymous user can visit a private user's project. | ||||
| CVE-2025-68940 | 1 Gitea | 1 Gitea | 2025-12-26 | 3.1 Low |
| In Gitea before 1.22.5, branch deletion permissions are not adequately enforced after merging a pull request. | ||||
| CVE-2025-68939 | 1 Gitea | 1 Gitea | 2025-12-26 | 8.2 High |
| Gitea before 1.23.0 allows attackers to add attachments with forbidden file extensions by editing an attachment name via an attachment API. | ||||
| CVE-2025-68938 | 1 Gitea | 1 Gitea | 2025-12-26 | 4.3 Medium |
| Gitea before 1.25.2 mishandles authorization for deletion of releases. | ||||
| CVE-2022-42968 | 1 Gitea | 1 Gitea | 2025-05-14 | 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-46685 | 1 Gitea | 1 Gitea | 2025-04-23 | 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-2023-3515 | 1 Gitea | 1 Gitea | 2025-02-13 | 4.4 Medium |
| Open Redirect in GitHub repository go-gitea/gitea prior to 1.19.4. | ||||
| CVE-2022-38795 | 1 Gitea | 1 Gitea | 2024-11-21 | 6.5 Medium |
| In Gitea through 1.17.1, repo cloning can occur in the migration function. | ||||
| CVE-2022-38183 | 1 Gitea | 1 Gitea | 2024-11-21 | 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 | 2024-11-21 | 7.5 High |
| Gitea before 1.16.7 does not escape git fetch remote. | ||||
| CVE-2022-27313 | 1 Gitea | 1 Gitea | 2024-11-21 | 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 | 2024-11-21 | 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 | 2024-11-21 | 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 | 2024-11-21 | 7.1 High |
| Missing Authorization in GitHub repository go-gitea/gitea prior to 1.16.4. | ||||
| CVE-2021-45331 | 1 Gitea | 1 Gitea | 2024-11-21 | 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. | ||||