Gitea
by Go Gitea
Source repositories
CVEs (55)
| CVE | Vendor / Product | Sev | Risk | CVSS | EPSS | KEV | Published | Description |
|---|---|---|---|---|---|---|---|---|
| CVE-2026-20800 | 0.00 | — | 0.00 | Jan 22, 2026 | 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 | 0.00 | — | 0.00 | Jan 22, 2026 | 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 | 0.00 | — | 0.00 | Jan 22, 2026 | 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-0798 | 0.00 | — | 0.00 | Jan 22, 2026 | 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… | |||
| CVE-2025-69413 | 0.00 | — | 0.00 | Jan 1, 2026 | In Gitea before 1.25.2, /api/v1/user has different responses for failed authentication depending on whether a username exists. | |||
| CVE-2025-68946 | 0.00 | — | 0.00 | Dec 26, 2025 | In Gitea before 1.20.1, a forbidden URL scheme such as javascript: can be used for a link, aka XSS. | |||
| CVE-2025-68945 | 0.00 | — | 0.00 | Dec 26, 2025 | In Gitea before 1.21.2, an anonymous user can visit a private user's project. | |||
| CVE-2025-68944 | 0.00 | — | 0.00 | Dec 26, 2025 | Gitea before 1.22.2 sometimes mishandles the propagation of token scope for access control within one of its own package registries. | |||
| CVE-2025-68943 | 0.00 | — | 0.00 | Dec 26, 2025 | Gitea before 1.21.8 inadvertently discloses users' login times by allowing (for example) the lastlogintime explore/users sort order. | |||
| CVE-2025-68942 | 0.00 | — | 0.00 | Dec 26, 2025 | 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-68941 | 0.00 | — | 0.00 | Dec 26, 2025 | Gitea before 1.22.3 mishandles access to a private resource upon receiving an API token with scope limited to public resources. | |||
| CVE-2025-68940 | 0.00 | — | 0.00 | Dec 26, 2025 | In Gitea before 1.22.5, branch deletion permissions are not adequately enforced after merging a pull request. | |||
| CVE-2025-68939 | 0.00 | — | 0.00 | Dec 26, 2025 | 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 | 0.00 | — | 0.00 | Dec 26, 2025 | Gitea before 1.25.2 mishandles authorization for deletion of releases. | |||
| CVE-2022-38795 | 0.00 | — | 0.00 | Aug 7, 2023 | In Gitea through 1.17.1, repo cloning can occur in the migration function. | |||
| CVE-2023-3515 | 0.00 | — | 0.00 | Jul 5, 2023 | Open Redirect in GitHub repository go-gitea/gitea prior to 1.19.4. | |||
| CVE-2022-42968 | 0.00 | — | 0.01 | Oct 16, 2022 | Gitea before 1.17.3 does not sanitize and escape refs in the git backend. Arguments to git commands are mishandled. | |||
| CVE-2022-38183 | 0.00 | — | 0.01 | Aug 12, 2022 | 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… | |||
| CVE-2022-1928 | 0.00 | — | 0.01 | May 29, 2022 | Cross-site Scripting (XSS) - Stored in GitHub repository go-gitea/gitea prior to 1.16.9. | |||
| CVE-2022-27313 | 0.00 | — | 0.01 | May 3, 2022 | 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-2026-20800Jan 22, 2026risk 0.00cvss —epss 0.00
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-20750Jan 22, 2026risk 0.00cvss —epss 0.00
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-20736Jan 22, 2026risk 0.00cvss —epss 0.00
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-0798Jan 22, 2026risk 0.00cvss —epss 0.00
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…
- CVE-2025-69413Jan 1, 2026risk 0.00cvss —epss 0.00
In Gitea before 1.25.2, /api/v1/user has different responses for failed authentication depending on whether a username exists.
- CVE-2025-68946Dec 26, 2025risk 0.00cvss —epss 0.00
In Gitea before 1.20.1, a forbidden URL scheme such as javascript: can be used for a link, aka XSS.
- CVE-2025-68945Dec 26, 2025risk 0.00cvss —epss 0.00
In Gitea before 1.21.2, an anonymous user can visit a private user's project.
- CVE-2025-68944Dec 26, 2025risk 0.00cvss —epss 0.00
Gitea before 1.22.2 sometimes mishandles the propagation of token scope for access control within one of its own package registries.
- CVE-2025-68943Dec 26, 2025risk 0.00cvss —epss 0.00
Gitea before 1.21.8 inadvertently discloses users' login times by allowing (for example) the lastlogintime explore/users sort order.
- CVE-2025-68942Dec 26, 2025risk 0.00cvss —epss 0.00
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-68941Dec 26, 2025risk 0.00cvss —epss 0.00
Gitea before 1.22.3 mishandles access to a private resource upon receiving an API token with scope limited to public resources.
- CVE-2025-68940Dec 26, 2025risk 0.00cvss —epss 0.00
In Gitea before 1.22.5, branch deletion permissions are not adequately enforced after merging a pull request.
- CVE-2025-68939Dec 26, 2025risk 0.00cvss —epss 0.00
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-68938Dec 26, 2025risk 0.00cvss —epss 0.00
Gitea before 1.25.2 mishandles authorization for deletion of releases.
- CVE-2022-38795Aug 7, 2023risk 0.00cvss —epss 0.00
In Gitea through 1.17.1, repo cloning can occur in the migration function.
- CVE-2023-3515Jul 5, 2023risk 0.00cvss —epss 0.00
Open Redirect in GitHub repository go-gitea/gitea prior to 1.19.4.
- CVE-2022-42968Oct 16, 2022risk 0.00cvss —epss 0.01
Gitea before 1.17.3 does not sanitize and escape refs in the git backend. Arguments to git commands are mishandled.
- CVE-2022-38183Aug 12, 2022risk 0.00cvss —epss 0.01
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…
- CVE-2022-1928May 29, 2022risk 0.00cvss —epss 0.01
Cross-site Scripting (XSS) - Stored in GitHub repository go-gitea/gitea prior to 1.16.9.
- CVE-2022-27313May 3, 2022risk 0.00cvss —epss 0.01
An arbitrary file deletion vulnerability in Gitea v1.16.3 allows attackers to cause a Denial of Service (DoS) via deleting the configuration file.
Page 2 of 3