Gitea
52 vulnerabilities.
All published vulnerabilities with a CVE number in Gitea products, newest first, with severity and references.
| CVE | Summary | Published | CVSS |
|---|---|---|---|
| CVE-2026-20912 | Gitea: Gitea does not properly validate repository ownership when linking attachments to releases. An attachment uploaded to a private repository could … | 2026-01-22 | 9.1 |
| CVE-2026-20904 | Gitea: Gitea does not properly validate ownership when toggling OpenID URI visibility. An authenticated user may be able to change the visibility settings … | 2026-01-22 | 6.5 |
| CVE-2026-20897 | Gitea: 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 … | 2026-01-22 | 9.1 |
| CVE-2026-20888 | Gitea: Gitea does not properly verify authorization when canceling scheduled auto-merges via the web interface. A user with read access to pull requests … | 2026-01-22 | 4.3 |
| CVE-2026-20883 | Gitea: 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 … | 2026-01-22 | 6.5 |
| CVE-2026-20800 | Gitea: Gitea's notification API does not re-validate repository access permissions when returning notification details. After a user's access to a private … | 2026-01-22 | 6.5 |
| CVE-2026-20750 | Gitea: Gitea does not properly validate project ownership in organization project operations. A user with project write access in one organization may be … | 2026-01-22 | 9.1 |
| CVE-2026-20736 | Gitea: Gitea does not properly verify repository context when deleting attachments. A user who previously uploaded an attachment to a repository may be … | 2026-01-22 | 7.5 |
| CVE-2026-0798 | Gitea: Gitea may send release notification emails for private repositories to users whose access has been revoked. When a repository is changed from … | 2026-01-22 | 3.5 |
| CVE-2025-69413 | Gitea: In Gitea before 1.25.2, /api/v1/user has different responses for failed authentication depending on whether a username exists. | 2026-01-01 | 5.3 |
| CVE-2025-68946 | Gitea: In Gitea before 1.20.1, a forbidden URL scheme such as javascript: can be used for a link, aka XSS. | 2025-12-26 | 5.4 |
| CVE-2025-68945 | Gitea: In Gitea before 1.21.2, an anonymous user can visit a private user's project. | 2025-12-26 | 5.8 |
| CVE-2025-68944 | Gitea: Gitea before 1.22.2 sometimes mishandles the propagation of token scope for access control within one of its own package registries. | 2025-12-26 | 5.0 |
| CVE-2025-68943 | Gitea: Gitea before 1.21.8 inadvertently discloses users' login times by allowing (for example) the lastlogintime explore/users sort order. | 2025-12-26 | 5.3 |
| CVE-2025-68942 | Gitea: Gitea before 1.22.2 allows XSS because the search input box (for creating tags and branches) is v-html instead of v-text. | 2025-12-26 | 5.4 |
| CVE-2025-68941 | Gitea: Gitea before 1.22.3 mishandles access to a private resource upon receiving an API token with scope limited to public resources. | 2025-12-26 | 4.9 |
| CVE-2025-68940 | Gitea: In Gitea before 1.22.5, branch deletion permissions are not adequately enforced after merging a pull request. | 2025-12-26 | 3.1 |
| CVE-2025-68939 | Gitea: Gitea before 1.23.0 allows attackers to add attachments with forbidden file extensions by editing an attachment name via an attachment API. | 2025-12-26 | 8.2 |
| CVE-2025-68938 | Gitea: Gitea before 1.25.2 mishandles authorization for deletion of releases. | 2025-12-26 | 4.3 |
| CVE-2023-3515 | Gitea: Open Redirect in GitHub repository go-gitea/gitea prior to 1.19.4. | 2023-07-05 | 4.4 |
| CVE-2022-46685 | Gitea: In Jenkins Gitea Plugin 1.4.4 and earlier, the implementation of Gitea personal access tokens did not support credentials masking, potentially … | 2022-12-12 | 4.3 |
| CVE-2022-42968 | Gitea: Gitea before 1.17.3 does not sanitize and escape refs in the git backend. Arguments to git commands are mishandled. | 2022-10-16 | 9.8 |
| CVE-2022-38795 | Gitea: In Gitea through 1.17.1, repo cloning can occur in the migration function. | 2023-08-07 | 6.5 |
| CVE-2022-38183 | Gitea: 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 … | 2022-08-12 | 6.5 |
| CVE-2022-30781 | Gitea: Gitea before 1.16.7 does not escape git fetch remote. | 2022-05-16 | 7.5 |
| CVE-2022-27313 | Gitea: An arbitrary file deletion vulnerability in Gitea v1.16.3 allows attackers to cause a Denial of Service (DoS) via deleting the configuration file. | 2022-05-03 | 7.5 |
| CVE-2022-1928 | Gitea: Cross-site Scripting (XSS) - Stored in GitHub repository go-gitea/gitea prior to 1.16.9. | 2022-05-29 | 5.4 |
| CVE-2022-1058 | Gitea: Open Redirect on login in GitHub repository go-gitea/gitea prior to 1.16.5. | 2022-03-24 | 6.1 |
| CVE-2022-0905 | Gitea: Missing Authorization in GitHub repository go-gitea/gitea prior to 1.16.4. | 2022-03-10 | 7.1 |
| CVE-2021-45331 | Gitea: An Authentication Bypass vulnerability exists in Gitea before 1.5.0, which could let a malicious user gain privileges. If captured, the TOTP code … | 2022-02-09 | 9.8 |
| CVE-2021-45330 | Gitea: 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 … | 2022-02-09 | 9.8 |
| CVE-2021-45329 | Gitea: Cross Site Scripting (XSS) vulnerability exists in Gitea before 1.5.1 via the repository settings inside the external wiki/issue tracker URL field. | 2022-02-08 | 6.1 |
| CVE-2021-45328 | Gitea: Gitea before 1.4.3 is affected by URL Redirection to Untrusted Site ('Open Redirect') via internal URLs. | 2022-02-08 | 6.1 |
| CVE-2021-45327 | Gitea: 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 … | 2022-02-08 | 9.8 |
| CVE-2021-45326 | Gitea: Cross Site Request Forgery (CSRF) vulnerability exists in Gitea before 1.5.2 via API routes.This can be dangerous especially with state altering … | 2022-02-08 | 8.8 |
| CVE-2021-45325 | Gitea: Server Side Request Forgery (SSRF) vulneraility exists in Gitea before 1.7.0 using the OpenID URL. | 2022-02-08 | 7.5 |
| CVE-2021-29134 | Gitea: The avatar middleware in Gitea before 1.13.6 allows Directory Traversal via a crafted URL. | 2022-03-15 | 5.3 |
| CVE-2021-28378 | Gitea: Gitea 1.12.x and 1.13.x before 1.13.4 allows XSS via certain issue data in some situations. | 2021-03-15 | 3.7 |
| CVE-2021-3382 | Gitea: 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 … | 2021-02-05 | 7.5 |
| CVE-2020-28991 | Gitea: 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 … | 2020-11-24 | 9.8 |
| CVE-2020-14144 | Gitea: The git hook feature in Gitea 1.1.0 through 1.12.5 might allow for authenticated remote code execution in customer environments where the … | 2020-10-16 | 7.2 |
| CVE-2020-13246 | Gitea: An issue was discovered in Gitea through 1.11.5. An attacker can trigger a deadlock by initiating a transfer of a repository's ownership from one … | 2020-05-20 | 7.5 |
| CVE-2019-1010314 | Gitea: Gitea 1.7.2, 1.7.3 is affected by: Cross Site Scripting (XSS). The impact is: execute JavaScript in victim's browser, when the vulnerable repo page … | 2019-07-11 | 6.1 |
| CVE-2019-1010261 | Gitea: Gitea 1.7.0 and earlier is affected by: Cross Site Scripting (XSS). The impact is: Attacker is able to have victim execute arbitrary JS in browser. … | 2019-07-18 | 6.1 |
| CVE-2019-1000002 | Gitea: Gitea version 1.6.2 and earlier contains a Incorrect Access Control vulnerability in Delete/Edit file functionallity that can result in the … | 2019-02-04 | 6.5 |
| CVE-2019-11576 | Gitea: Gitea before 1.8.0 allows 1FA for user accounts that have completed 2FA enrollment. If a user's credentials are known, then an attacker could send … | 2019-04-28 | 9.8 |
| CVE-2019-11229 | Gitea: models/repo_mirror.go in Gitea before 1.7.6 and 1.8.x before 1.8-RC3 mishandles mirror repo URL settings, leading to remote code execution. | 2019-04-15 | 8.8 |
| CVE-2019-11228 | Gitea: repo/setting.go in Gitea before 1.7.6 and 1.8.x before 1.8-RC3 does not validate the form.MirrorAddress before calling SaveAddress. | 2019-04-15 | 7.5 |
| CVE-2019-10330 | Gitea: Jenkins Gitea Plugin 1.1.1 and earlier did not implement trusted revisions, allowing attackers without commit access to the Git repo to change … | 2019-05-31 | 7.5 |
| CVE-2018-1000803 | Gitea: Gitea version prior to version 1.5.1 contains a CWE-200 vulnerability that can result in Exposure of users private email addresses. This attack … | 2018-10-08 | 5.3 |
| CVE-2018-18926 | Gitea: Gitea before 1.5.4 allows remote code execution because it does not properly validate session IDs. This is related to session ID handling in the … | 2018-11-04 | 9.8 |
| CVE-2018-15192 | Gitea: An SSRF vulnerability in webhooks in Gitea through 1.5.0-rc2 and Gogs through 0.11.53 allows remote attackers to access intranet services. | 2018-08-08 | 8.6 |
Data: CVE list and the NVD. This product uses data from the NVD API but is not endorsed or certified by the NVD.
Too many to
patch at once?
Providers for vulnerability management find the affected systems in your environment, set the order and keep the patching going.