Gitea
by Go Gitea
Source repositories
CVEs (265)
| CVE | Vendor / Product | Sev | Risk | CVSS | EPSS | KEV | Published | Description |
|---|---|---|---|---|---|---|---|---|
| CVE-2026-58427 | Hig | 0.42 | 7.5 | 0.00 | Aug 13, 2026 | Private org member list leaked via /members API endpoint — incomplete fix for PR #38145 | ||
| CVE-2026-58417 | Hig | 0.42 | 7.5 | 0.00 | Aug 13, 2026 | REST API exposes organization membership of private organizations to public | ||
| CVE-2026-42931 | Med | 0.42 | 6.5 | 0.01 | Aug 13, 2026 | Denial of Service via Unbounded io.ReadAll in NPM Package Tag Endpoint | ||
| CVE-2026-34966 | Hig | 0.42 | 7.6 | 0.00 | Aug 5, 2026 | Gitea prior to 1.27.0 contains a server-side request forgery vulnerability that allows authenticated attackers to bypass SSRF protections by exploiting HTTP fetch operations in migration and OAuth avatar code paths that use Go's default http.Get without a custom DialContext.… | ||
| CVE-2026-58421 | Hig | 0.42 | 7.5 | 0.00 | Jul 3, 2026 | Unauthenticated ReDoS via CODEOWNERS pattern matching allows denial of service | ||
| CVE-2026-58419 | Hig | 0.42 | 7.5 | 0.00 | Jul 3, 2026 | Notification API leaks private issue metadata after access revocation | ||
| CVE-2026-27779 | Hig | 0.42 | 7.5 | 0.01 | Jul 3, 2026 | Gitea versions before 1.25.5 accept malformed or injected forwarded-proto values when detecting public URLs, allowing spoofed canonical URL generation. | ||
| CVE-2026-27660 | Hig | 0.42 | 7.5 | 0.00 | Jul 3, 2026 | Gitea versions before 1.25.5 allow draft release data or attachments to be accessed without the required write permission. | ||
| CVE-2026-27657 | Hig | 0.42 | 7.5 | 0.00 | Jul 3, 2026 | Gitea versions before 1.25.5 allow a user to change another user's primary email address. | ||
| CVE-2026-26307 | Hig | 0.42 | 7.5 | 0.01 | Jul 3, 2026 | Gitea versions before 1.25.5 do not enforce a timeout on git grep searches, allowing expensive searches to consume server resources. | ||
| CVE-2026-25712 | Hig | 0.42 | 7.5 | 0.00 | Jul 3, 2026 | Gitea versions before 1.25.5 have insufficient visibility checks in organization permission APIs for hidden members and private organizations. | ||
| CVE-2026-25038 | Hig | 0.42 | 7.5 | 0.01 | Jul 3, 2026 | Gitea 1.26.2 allows unauthorized users to access labels of private organizations. | ||
| CVE-2026-24690 | Hig | 0.42 | 7.5 | 0.00 | Jul 3, 2026 | Gitea versions before 1.25.5 have insufficient permission checks for updating or rebasing pull request branches. | ||
| CVE-2026-24451 | Hig | 0.42 | 7.5 | 0.00 | Jul 3, 2026 | Gitea 1.26.2 allows fork synchronization to continue after a parent repository changes from public to private, exposing data to a fork that should no longer be authorized. | ||
| CVE-2026-20736 | Hig | 0.42 | 7.5 | 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-2022-27313 | Hig | 0.42 | 7.5 | 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-2021-39867 | Med | 0.42 | 6.5 | 0.01 | Oct 5, 2021 | In all versions of GitLab CE/EE since version 8.15, a DNS rebinding vulnerability in Gitea Importer may be exploited by an attacker to trigger Server Side Request Forgery (SSRF) attacks. | ||
| CVE-2019-10330 | Hig | 0.42 | 7.5 | 0.02 | May 31, 2019 | Jenkins Gitea Plugin 1.1.1 and earlier did not implement trusted revisions, allowing attackers without commit access to the Git repo to change Jenkinsfiles even if Jenkins is configured to consider them to be untrusted. | ||
| CVE-2019-1000002 | Med | 0.42 | 6.5 | 0.01 | Feb 4, 2019 | Gitea version 1.6.2 and earlier contains a Incorrect Access Control vulnerability in Delete/Edit file functionallity that can result in the attacker deleting files outside the repository he/she has access to. This attack appears to be exploitable via the attacker must get write… | ||
| CVE-2026-58441 | Med | 0.41 | 6.3 | 0.00 | Aug 13, 2026 | SSRF in restore-repo via unsanitized pull_request.yml Head.CloneURL |
- risk 0.42cvss 7.5epss 0.00
Private org member list leaked via /members API endpoint — incomplete fix for PR #38145
- risk 0.42cvss 7.5epss 0.00
REST API exposes organization membership of private organizations to public
- risk 0.42cvss 6.5epss 0.01
Denial of Service via Unbounded io.ReadAll in NPM Package Tag Endpoint
- risk 0.42cvss 7.6epss 0.00
Gitea prior to 1.27.0 contains a server-side request forgery vulnerability that allows authenticated attackers to bypass SSRF protections by exploiting HTTP fetch operations in migration and OAuth avatar code paths that use Go's default http.Get without a custom DialContext.…
- risk 0.42cvss 7.5epss 0.00
Unauthenticated ReDoS via CODEOWNERS pattern matching allows denial of service
- risk 0.42cvss 7.5epss 0.00
Notification API leaks private issue metadata after access revocation
- risk 0.42cvss 7.5epss 0.01
Gitea versions before 1.25.5 accept malformed or injected forwarded-proto values when detecting public URLs, allowing spoofed canonical URL generation.
- risk 0.42cvss 7.5epss 0.00
Gitea versions before 1.25.5 allow draft release data or attachments to be accessed without the required write permission.
- risk 0.42cvss 7.5epss 0.00
Gitea versions before 1.25.5 allow a user to change another user's primary email address.
- risk 0.42cvss 7.5epss 0.01
Gitea versions before 1.25.5 do not enforce a timeout on git grep searches, allowing expensive searches to consume server resources.
- risk 0.42cvss 7.5epss 0.00
Gitea versions before 1.25.5 have insufficient visibility checks in organization permission APIs for hidden members and private organizations.
- risk 0.42cvss 7.5epss 0.01
Gitea 1.26.2 allows unauthorized users to access labels of private organizations.
- risk 0.42cvss 7.5epss 0.00
Gitea versions before 1.25.5 have insufficient permission checks for updating or rebasing pull request branches.
- risk 0.42cvss 7.5epss 0.00
Gitea 1.26.2 allows fork synchronization to continue after a parent repository changes from public to private, exposing data to a fork that should no longer be authorized.
- risk 0.42cvss 7.5epss 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.
- risk 0.42cvss 7.5epss 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.
- risk 0.42cvss 6.5epss 0.01
In all versions of GitLab CE/EE since version 8.15, a DNS rebinding vulnerability in Gitea Importer may be exploited by an attacker to trigger Server Side Request Forgery (SSRF) attacks.
- risk 0.42cvss 7.5epss 0.02
Jenkins Gitea Plugin 1.1.1 and earlier did not implement trusted revisions, allowing attackers without commit access to the Git repo to change Jenkinsfiles even if Jenkins is configured to consider them to be untrusted.
- risk 0.42cvss 6.5epss 0.01
Gitea version 1.6.2 and earlier contains a Incorrect Access Control vulnerability in Delete/Edit file functionallity that can result in the attacker deleting files outside the repository he/she has access to. This attack appears to be exploitable via the attacker must get write…
- risk 0.41cvss 6.3epss 0.00
SSRF in restore-repo via unsanitized pull_request.yml Head.CloneURL
Page 6 of 14