Go modules package
code.gitea.io/gitea
pkg:golang/code.gitea.io/gitea
Vulnerabilities (35)
| CVE | Sev | CVSS | KEV | Affected versions | Fixed in | Published | Description |
|---|---|---|---|---|---|---|---|
| CVE-2026-24791 | Hig | 8.1 | >= 1.22.3, < 1.26.2 | 1.26.2 | Aug 13, 2026 | Public-only tokens bypass private-resource restrictions on `/api/v1/user` self routes | |
| CVE-2026-28737 | Hig | 8.7 | >= 1.25.0, < 1.26.0 | 1.26.0 | Jul 3, 2026 | Gitea versions from 1.25.0 before 1.26.0 allow stored cross-site scripting through the extensionsRequired field in glTF files rendered by the 3D file viewer. | |
| CVE-2026-22555 | Hig | 8.1 | < 1.26.0 | 1.26.0 | Jul 3, 2026 | Gitea versions before 1.26.0 allow API users to fork a repository into an organization without first passing the CanCreateOrgRepo check, which can expose organization secrets. | |
| CVE-2026-20736 | Hig | 7.5 | < 1.25.4 | 1.25.4 | 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 | Low | 3.5 | < 1.25.4 | 1.25.4 | 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 relea | |
| CVE-2025-69413 | Med | 5.3 | < 1.25.2 | 1.25.2 | 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 | Med | 5.4 | < 1.20.1 | 1.20.1 | 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 | Med | 5.8 | < 1.21.2 | 1.21.2 | Dec 26, 2025 | In Gitea before 1.21.2, an anonymous user can visit a private user's project. | |
| CVE-2025-68944 | Med | 5.0 | < 1.22.2 | 1.22.2 | 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 | Med | 5.3 | < 1.21.8 | 1.21.8 | 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 | Med | 5.4 | < 1.22.2 | 1.22.2 | 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 | Med | 4.9 | < 1.22.3 | 1.22.3 | 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 | Low | 3.1 | < 1.22.5 | 1.22.5 | Dec 26, 2025 | In Gitea before 1.22.5, branch deletion permissions are not adequately enforced after merging a pull request. | |
| CVE-2025-68939 | Hig | 8.2 | >= 0 | — | 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 | Med | 4.3 | < 1.25.2 | 1.25.2 | Dec 26, 2025 | Gitea before 1.25.2 mishandles authorization for deletion of releases. | |
| CVE-2024-6886 | Cri | — | < 1.22.1 | 1.22.1 | Aug 6, 2024 | Improper Neutralization of Input During Web Page Generation (XSS or 'Cross-site Scripting') vulnerability in Gitea Gitea Open Source Git Server allows Stored XSS.This issue affects Gitea Open Source Git Server: 1.22.0. | |
| CVE-2022-38795 | Med | 6.5 | < 1.17.2 | 1.17.2 | Aug 7, 2023 | In Gitea through 1.17.1, repo cloning can occur in the migration function. | |
| CVE-2023-3515 | Med | 4.4 | < 1.19.4 | 1.19.4 | Jul 5, 2023 | Open Redirect in GitHub repository go-gitea/gitea prior to 1.19.4. | |
| CVE-2022-38183 | Med | 6.5 | < 1.16.9 | 1.16.9 | 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 | Med | 5.4 | < 1.16.9 | 1.16.9 | May 29, 2022 | Cross-site Scripting (XSS) - Stored in GitHub repository go-gitea/gitea prior to 1.16.9. |
- affected >= 1.22.3, < 1.26.2fixed 1.26.2
Public-only tokens bypass private-resource restrictions on `/api/v1/user` self routes
- affected >= 1.25.0, < 1.26.0fixed 1.26.0
Gitea versions from 1.25.0 before 1.26.0 allow stored cross-site scripting through the extensionsRequired field in glTF files rendered by the 3D file viewer.
- affected < 1.26.0fixed 1.26.0
Gitea versions before 1.26.0 allow API users to fork a repository into an organization without first passing the CanCreateOrgRepo check, which can expose organization secrets.
- affected < 1.25.4fixed 1.25.4
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.
- affected < 1.25.4fixed 1.25.4
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 relea
- affected < 1.25.2fixed 1.25.2
In Gitea before 1.25.2, /api/v1/user has different responses for failed authentication depending on whether a username exists.
- affected < 1.20.1fixed 1.20.1
In Gitea before 1.20.1, a forbidden URL scheme such as javascript: can be used for a link, aka XSS.
- affected < 1.21.2fixed 1.21.2
In Gitea before 1.21.2, an anonymous user can visit a private user's project.
- affected < 1.22.2fixed 1.22.2
Gitea before 1.22.2 sometimes mishandles the propagation of token scope for access control within one of its own package registries.
- affected < 1.21.8fixed 1.21.8
Gitea before 1.21.8 inadvertently discloses users' login times by allowing (for example) the lastlogintime explore/users sort order.
- affected < 1.22.2fixed 1.22.2
Gitea before 1.22.2 allows XSS because the search input box (for creating tags and branches) is v-html instead of v-text.
- affected < 1.22.3fixed 1.22.3
Gitea before 1.22.3 mishandles access to a private resource upon receiving an API token with scope limited to public resources.
- affected < 1.22.5fixed 1.22.5
In Gitea before 1.22.5, branch deletion permissions are not adequately enforced after merging a pull request.
- affected >= 0
Gitea before 1.23.0 allows attackers to add attachments with forbidden file extensions by editing an attachment name via an attachment API.
- affected < 1.25.2fixed 1.25.2
Gitea before 1.25.2 mishandles authorization for deletion of releases.
- affected < 1.22.1fixed 1.22.1
Improper Neutralization of Input During Web Page Generation (XSS or 'Cross-site Scripting') vulnerability in Gitea Gitea Open Source Git Server allows Stored XSS.This issue affects Gitea Open Source Git Server: 1.22.0.
- affected < 1.17.2fixed 1.17.2
In Gitea through 1.17.1, repo cloning can occur in the migration function.
- affected < 1.19.4fixed 1.19.4
Open Redirect in GitHub repository go-gitea/gitea prior to 1.19.4.
- affected < 1.16.9fixed 1.16.9
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
- affected < 1.16.9fixed 1.16.9
Cross-site Scripting (XSS) - Stored in GitHub repository go-gitea/gitea prior to 1.16.9.
Page 1 of 2