Gitea
by Go Gitea
Source repositories
CVEs (146)
| CVE | Vendor / Product | Sev | Risk | CVSS | EPSS | KEV | Published | Description |
|---|---|---|---|---|---|---|---|---|
| CVE-2025-68937 | Cri | 0.62 | — | 0.00 | Dec 26, 2025 | Forgejo before 13.0.2 allows attackers to write to unintended files, and possibly obtain server shell access, because of mishandling of out-of-repository symlink destinations for template repositories. This is also fixed for 11 LTS in 11.0.7 and later. | ||
| CVE-2024-6886 | Cri | 0.61 | — | 0.33 | 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-2026-20896 | Cri | 0.59 | 9.8 | 0.32 | Jul 3, 2026 | Gitea Docker image versions up to and including 1.26.2 use REVERSE_PROXY_TRUSTED_PROXIES=* by default, allowing any source IP to impersonate a user when reverse-proxy authentication headers such as X-WEBAUTH-USER are enabled. | ||
| CVE-2026-58422 | Cri | 0.57 | 9.8 | 0.00 | Jul 3, 2026 | Improper authorization on OAuth sign-in callback silently re-enables administrator-disabled accounts | ||
| CVE-2026-28737 | Hig | 0.57 | 8.7 | 0.00 | 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-2022-42968 | Cri | 0.57 | 9.8 | 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-2021-45327 | Cri | 0.57 | 9.8 | 0.02 | Feb 8, 2022 | 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 could let a remote malisious user execute arbitrary code. | ||
| CVE-2018-18926 | Cri | 0.57 | 9.8 | 0.03 | Nov 4, 2018 | 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 go-macaron/session code for Macaron. | ||
| CVE-2026-58426 | Cri | 0.55 | 9.6 | 0.00 | Jul 3, 2026 | Gitea Actions Artifacts V4 signed URL HMAC ambiguity allows cross-repository artifact read and cross-task upload-state write | ||
| CVE-2026-20706 | Cri | 0.52 | 9.1 | 0.00 | Jul 3, 2026 | Gitea versions up to and including 1.26.1 allow repository archive downloads to bypass token scope checks on the web archive download endpoint. | ||
| CVE-2026-20912 | Cri | 0.52 | 9.1 | 0.00 | Jan 22, 2026 | Gitea does not properly validate repository ownership when linking attachments to releases. An attachment uploaded to a private repository could potentially be linked to a release in a different public repository, making it accessible to unauthorized users. | ||
| CVE-2026-20897 | Cri | 0.52 | 9.1 | 0.00 | Jan 22, 2026 | 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 LFS locks belonging to other repositories. | ||
| CVE-2026-20750 | Cri | 0.52 | 9.1 | 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-2022-30781 | Hig | 0.52 | 7.5 | 0.88 | May 16, 2022 | Gitea before 1.16.7 does not escape git fetch remote. | ||
| CVE-2026-58424 | Hig | 0.51 | 8.9 | 0.00 | Jul 3, 2026 | Permanent Fork PR Workflow Approval Gate Bypass | ||
| CVE-2026-27775 | Hig | 0.50 | 8.8 | 0.01 | Jul 3, 2026 | Gitea 1.25.5 caches a branch-specific write-permission result across multiple refs in one pre-receive hook session, allowing a per-branch maintainer-edit grant to be reused for other refs and escalate to full repository write access. | ||
| CVE-2020-14144 | Hig | 0.50 | 7.2 | 0.95 | Oct 16, 2020 | 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 documentation was not understood (e.g., one viewpoint is that the dangerousness of this feature should be documented immediately above the… | ||
| CVE-2018-15192 | Hig | 0.49 | 8.6 | 0.02 | Aug 8, 2018 | 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. | ||
| CVE-2026-26231 | Hig | 0.48 | 8.5 | 0.00 | Jul 3, 2026 | Gitea versions up to and including 1.26.1 allow the Allow edits from maintainers permission path to authorize commits to repositories that the user can read but should not be able to write. | ||
| CVE-2026-24791 | Hig | 0.46 | 8.1 | — | Aug 13, 2026 | Public-only tokens bypass private-resource restrictions on `/api/v1/user` self routes |
- risk 0.62cvss —epss 0.00
Forgejo before 13.0.2 allows attackers to write to unintended files, and possibly obtain server shell access, because of mishandling of out-of-repository symlink destinations for template repositories. This is also fixed for 11 LTS in 11.0.7 and later.
- risk 0.61cvss —epss 0.33
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.
- risk 0.59cvss 9.8epss 0.32
Gitea Docker image versions up to and including 1.26.2 use REVERSE_PROXY_TRUSTED_PROXIES=* by default, allowing any source IP to impersonate a user when reverse-proxy authentication headers such as X-WEBAUTH-USER are enabled.
- risk 0.57cvss 9.8epss 0.00
Improper authorization on OAuth sign-in callback silently re-enables administrator-disabled accounts
- risk 0.57cvss 8.7epss 0.00
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.
- risk 0.57cvss 9.8epss 0.01
Gitea before 1.17.3 does not sanitize and escape refs in the git backend. Arguments to git commands are mishandled.
- risk 0.57cvss 9.8epss 0.02
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 could let a remote malisious user execute arbitrary code.
- risk 0.57cvss 9.8epss 0.03
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 go-macaron/session code for Macaron.
- risk 0.55cvss 9.6epss 0.00
Gitea Actions Artifacts V4 signed URL HMAC ambiguity allows cross-repository artifact read and cross-task upload-state write
- risk 0.52cvss 9.1epss 0.00
Gitea versions up to and including 1.26.1 allow repository archive downloads to bypass token scope checks on the web archive download endpoint.
- risk 0.52cvss 9.1epss 0.00
Gitea does not properly validate repository ownership when linking attachments to releases. An attachment uploaded to a private repository could potentially be linked to a release in a different public repository, making it accessible to unauthorized users.
- risk 0.52cvss 9.1epss 0.00
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 LFS locks belonging to other repositories.
- risk 0.52cvss 9.1epss 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.
- risk 0.52cvss 7.5epss 0.88
Gitea before 1.16.7 does not escape git fetch remote.
- risk 0.51cvss 8.9epss 0.00
Permanent Fork PR Workflow Approval Gate Bypass
- risk 0.50cvss 8.8epss 0.01
Gitea 1.25.5 caches a branch-specific write-permission result across multiple refs in one pre-receive hook session, allowing a per-branch maintainer-edit grant to be reused for other refs and escalate to full repository write access.
- risk 0.50cvss 7.2epss 0.95
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 documentation was not understood (e.g., one viewpoint is that the dangerousness of this feature should be documented immediately above the…
- risk 0.49cvss 8.6epss 0.02
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.
- risk 0.48cvss 8.5epss 0.00
Gitea versions up to and including 1.26.1 allow the Allow edits from maintainers permission path to authorize commits to repositories that the user can read but should not be able to write.
- risk 0.46cvss 8.1epss —
Public-only tokens bypass private-resource restrictions on `/api/v1/user` self routes
Page 1 of 8