Filtered by vendor Gitea
Subscribe
Total
52 CVE
| CVE | Vendors | Products | Updated | CVSS v2 | CVSS v3 |
|---|---|---|---|---|---|
| CVE-2026-20912 | 1 Gitea | 1 Gitea | 2026-01-29 | N/A | 9.1 CRITICAL |
|
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.
|
|||||
| CVE-2026-20904 | 1 Gitea | 1 Gitea | 2026-01-29 | 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-20897 | 1 Gitea | 1 Gitea | 2026-01-29 | 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-20888 | 1 Gitea | 1 Gitea | 2026-01-29 | 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-0798 | 1 Gitea | 1 Gitea | 2026-01-29 | 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-2026-20883 | 1 Gitea | 1 Gitea | 2026-01-29 | 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-01-29 | 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-20750 | 1 Gitea | 1 Gitea | 2026-01-29 | 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-01-29 | 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-2025-69413 | 1 Gitea | 1 Gitea | 2026-01-06 | N/A | 5.3 MEDIUM |
|
In Gitea before 1.25.2, /api/v1/user has different responses for failed authentication depending on whether a username exists.
|
|||||
| CVE-2025-68938 | 1 Gitea | 1 Gitea | 2026-01-02 | N/A | 4.3 MEDIUM |
|
Gitea before 1.25.2 mishandles authorization for deletion of releases.
|
|||||
| CVE-2025-68939 | 1 Gitea | 1 Gitea | 2026-01-02 | N/A | 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-68940 | 1 Gitea | 1 Gitea | 2026-01-02 | N/A | 3.1 LOW |
|
In Gitea before 1.22.5, branch deletion permissions are not adequately enforced after merging a pull request.
|
|||||
| CVE-2025-68941 | 1 Gitea | 1 Gitea | 2026-01-02 | N/A | 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 | 2026-01-02 | N/A | 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-31 | N/A | 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-31 | N/A | 5.0 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-68945 | 1 Gitea | 1 Gitea | 2025-12-31 | N/A | 5.8 MEDIUM |
|
In Gitea before 1.21.2, an anonymous user can visit a private user's project.
|
|||||
| CVE-2025-68946 | 1 Gitea | 1 Gitea | 2025-12-31 | N/A | 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-2022-42968 | 1 Gitea | 1 Gitea | 2025-05-14 | 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-46685 | 1 Gitea | 1 Gitea | 2025-04-23 | 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-2023-3515 | 1 Gitea | 1 Gitea | 2024-11-21 | N/A | 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 | 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 | 2024-11-21 | 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 | 2024-11-21 | 5.0 MEDIUM | 7.5 HIGH |
|
Gitea before 1.16.7 does not escape git fetch remote.
|
|||||
| CVE-2022-27313 | 1 Gitea | 1 Gitea | 2024-11-21 | 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 | 2024-11-21 | 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 | 2024-11-21 | 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 | 2024-11-21 | 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 | 2024-11-21 | 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 | 2024-11-21 | 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.
|
|||||
| CVE-2021-45329 | 1 Gitea | 1 Gitea | 2024-11-21 | 4.3 MEDIUM | 6.1 MEDIUM |
|
Cross Site Scripting (XSS) vulnerability exists in Gitea before 1.5.1 via the repository settings inside the external wiki/issue tracker URL field.
|
|||||
| CVE-2021-45328 | 1 Gitea | 1 Gitea | 2024-11-21 | 5.8 MEDIUM | 6.1 MEDIUM |
|
Gitea before 1.4.3 is affected by URL Redirection to Untrusted Site ('Open Redirect') via internal URLs.
|
|||||
| CVE-2021-45327 | 1 Gitea | 1 Gitea | 2024-11-21 | 7.5 HIGH | 9.8 CRITICAL |
|
Gitea before 1.11.2 is affected by Trusting HTTP Permission Methods on the Server Side when referencing the vulnerable admin or user API. which could let a remote malisious user execute arbitrary code.
|
|||||
| CVE-2021-45326 | 1 Gitea | 1 Gitea | 2024-11-21 | 6.8 MEDIUM | 8.8 HIGH |
|
Cross Site Request Forgery (CSRF) vulnerability exists in Gitea before 1.5.2 via API routes.This can be dangerous especially with state altering POST requests.
|
|||||
| CVE-2021-45325 | 1 Gitea | 1 Gitea | 2024-11-21 | 5.0 MEDIUM | 7.5 HIGH |
|
Server Side Request Forgery (SSRF) vulneraility exists in Gitea before 1.7.0 using the OpenID URL.
|
|||||
| CVE-2021-3382 | 1 Gitea | 1 Gitea | 2024-11-21 | 5.0 MEDIUM | 7.5 HIGH |
|
Stack buffer overflow vulnerability in gitea 1.9.0 through 1.13.1 allows remote attackers to cause a denial of service (crash) via vectors related to a file path.
|
|||||
| CVE-2021-29134 | 1 Gitea | 1 Gitea | 2024-11-21 | 5.0 MEDIUM | 5.3 MEDIUM |
|
The avatar middleware in Gitea before 1.13.6 allows Directory Traversal via a crafted URL.
|
|||||
| CVE-2021-28378 | 1 Gitea | 1 Gitea | 2024-11-21 | 3.5 LOW | 3.7 LOW |
|
Gitea 1.12.x and 1.13.x before 1.13.4 allows XSS via certain issue data in some situations.
|
|||||
| CVE-2020-28991 | 1 Gitea | 1 Gitea | 2024-11-21 | 7.5 HIGH | 9.8 CRITICAL |
|
Gitea 0.9.99 through 1.12.x before 1.12.6 does not prevent a git protocol path that specifies a TCP port number and also contains newlines (with URL encoding) in ParseRemoteAddr in modules/auth/repo_form.go.
|
|||||