← Back

Gitea

gitea

81 CVEs • 1 product

Products (1)

Click to collapse
Toggle
Gitea
gitea

CVEs (81)

CVE
VENDORS
PRODUCTS
UPDATED
PUBLISHED
CVSS
1Gitea
1Gitea
Oct 13, 2026
Dec 26, 2025
N/A· v4
5.3 MEDIUM· v3
N/A· v2
In Gitea before 1.21.2, an anonymous user can visit a private user's project.
1Gitea
1Gitea
Oct 13, 2026
Dec 26, 2025
N/A· v4
5.3 MEDIUM· v3
N/A· v2
Gitea before 1.22.2 sometimes mishandles the propagation of token scope for access control within one of its own package registries.
1Gitea
1Gitea
Oct 13, 2026
Dec 26, 2025
N/A· v4
5.3 MEDIUM· v3
N/A· v2
Gitea before 1.21.8 inadvertently discloses users' login times by allowing (for example) the lastlogintime explore/users sort order.
1Gitea
1Gitea
Oct 13, 2026
Dec 26, 2025
N/A· v4
5.4 MEDIUM· v3
N/A· v2
Gitea before 1.22.2 allows XSS because the search input box (for creating tags and branches) is v-html instead of v-text.
1Gitea
1Gitea
Oct 13, 2026
Dec 26, 2025
N/A· v4
5.3 MEDIUM· v3
N/A· v2
Gitea before 1.22.3 mishandles access to a private resource upon receiving an API token with scope limited to public resources.
1Gitea
1Gitea
Oct 13, 2026
Dec 26, 2025
N/A· v4
5.3 MEDIUM· v3
N/A· v2
In Gitea before 1.22.5, branch deletion permissions are not adequately enforced after merging a pull request.
1Gitea
1Gitea
Oct 13, 2026
Dec 26, 2025
N/A· v4
5.3 MEDIUM· v3
N/A· v2
Gitea before 1.23.0 allows attackers to add attachments with forbidden file extensions by editing an attachment name via an attachment API.
1Gitea
1Gitea
Oct 13, 2026
Dec 26, 2025
N/A· v4
5.3 MEDIUM· v3
N/A· v2
Gitea before 1.25.2 mishandles authorization for deletion of releases.
1Gitea
1Gitea
Jun 17, 2026
Aug 7, 2023
N/A· v4
6.5 MEDIUM· v3
N/A· v2
In Gitea through 1.17.1, repo cloning can occur in the migration function.
1Gitea
1Gitea
Jun 17, 2026
Jul 5, 2023
N/A· v4
4.4 MEDIUM· v3
N/A· v2
Open Redirect in GitHub repository go-gitea/gitea prior to 1.19.4.
1Gitea
1Gitea
Jun 17, 2026
Dec 12, 2022
N/A· v4
4.3 MEDIUM· v3
N/A· v2
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.
1Gitea
1Gitea
Jun 17, 2026
Oct 16, 2022
N/A· v4
9.8 CRITICAL· v3
N/A· v2
Gitea before 1.17.3 does not sanitize and escape refs in the git backend. Arguments to git commands are mishandled.
1Gitea
1Gitea
Jun 17, 2026
Aug 12, 2022
N/A· v4
6.5 MEDIUM· v3
N/A· v2
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 fetchin...Show more
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.Show less
1Gitea
1Gitea
Jun 17, 2026
May 29, 2022
N/A· v4
5.4 MEDIUM· v3
3.5 LOW· v2
Cross-site Scripting (XSS) - Stored in GitHub repository go-gitea/gitea prior to 1.16.9.
1Gitea
1Gitea
Jun 17, 2026
May 16, 2022
N/A· v4
7.5 HIGH· v3
5.0 MEDIUM· v2
Gitea before 1.16.7 does not escape git fetch remote.
1Gitea
1Gitea
Jun 17, 2026
May 3, 2022
N/A· v4
7.5 HIGH· v3
5.0 MEDIUM· v2
An arbitrary file deletion vulnerability in Gitea v1.16.3 allows attackers to cause a Denial of Service (DoS) via deleting the configuration file.
1Gitea
1Gitea
Jun 17, 2026
Mar 24, 2022
N/A· v4
6.1 MEDIUM· v3
5.8 MEDIUM· v2
Open Redirect on login in GitHub repository go-gitea/gitea prior to 1.16.5.
1Gitea
1Gitea
Jun 17, 2026
Mar 15, 2022
N/A· v4
5.3 MEDIUM· v3
5.0 MEDIUM· v2
The avatar middleware in Gitea before 1.13.6 allows Directory Traversal via a crafted URL.
1Gitea
1Gitea
Jun 17, 2026
Mar 10, 2022
N/A· v4
7.1 HIGH· v3
5.5 MEDIUM· v2
Missing Authorization in GitHub repository go-gitea/gitea prior to 1.16.4.
1Gitea
1Gitea
Jun 17, 2026
Feb 9, 2022
N/A· v4
9.8 CRITICAL· v3
7.5 HIGH· v2
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.