Gitea
by Go Gitea
Source repositories
CVEs (265)
| CVE | Vendor / Product | Sev | Risk | CVSS | EPSS | KEV | Published | Description |
|---|---|---|---|---|---|---|---|---|
| CVE-2026-56750 | Cri | 0.52 | 9.1 | 0.00 | Aug 13, 2026 | Gitea Remember-Me Token Theft Not Invalidating Attacker Session | ||
| CVE-2026-26247 | Cri | 0.52 | 9.1 | 0.01 | Jul 3, 2026 | Gitea versions before 1.25.5 do not persist the OAuth2 PKCE S256 challenge method correctly during authorization, allowing token exchange without the expected verifier check. | ||
| CVE-2026-26232 | Cri | 0.52 | 9.1 | 0.01 | Jul 3, 2026 | Gitea versions before 1.25.5 do not consistently enforce OAuth2 authorization code expiry and single-use behavior during token exchange. | ||
| CVE-2026-25718 | Cri | 0.52 | 9.1 | 0.01 | Jul 3, 2026 | Gitea versions before 1.25.5 mishandle path resolution during template repository generation, allowing template processing to read or write through symlinked or otherwise non-regular paths. | ||
| CVE-2026-22547 | Cri | 0.52 | 9.1 | 0.01 | Jul 3, 2026 | Gitea versions before 1.25.5 lack validation constraints for repository creation fields, including length-limited template fields and trust model or object format values. | ||
| CVE-2026-20706 | Cri | 0.52 | 9.1 | 0.01 | 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-73800 | Hig | 0.50 | 8.8 | 0.01 | Oct 14, 2026 | Gitea resolves local reusable workflow files from a fork's head commit when a trusted base-branch workflow runs for a pull_request_target event. A fork author can modify a referenced reusable workflow so attacker-controlled code executes with the repository and organization… | ||
| CVE-2026-73535 | Hig | 0.50 | 8.8 | 0.00 | Oct 14, 2026 | Gitea's OpenID connect handler accepts a user's password without enforcing enrolled TOTP or WebAuthn verification before completing sign-in and linking an OpenID identifier. When OpenID sign-in is enabled, an attacker who knows the victim's password can obtain a session and link… | ||
| CVE-2026-71184 | Hig | 0.50 | 8.8 | 0.00 | Oct 14, 2026 | Gitea's pull request review notifier does not attach the pull request to the Actions notification, so the fork workflow approval gate does not recognize the run as originating from a fork. Review comment and review approval or rejection events can consequently load workflow code… | ||
| CVE-2026-104632 | Hig | 0.50 | 8.8 | 0.00 | Oct 6, 2026 | Gitea Actions blocks the jobs of workflow runs from first-time fork pull request contributors until a maintainer approves the run. The rerun path only required a run to be finished and built the new attempt's jobs without considering the pending approval, so when a user with… | ||
| CVE-2026-104626 | Hig | 0.50 | 8.8 | 0.00 | Oct 6, 2026 | A user who can open a fork pull request can place workflow content with a shared run-level concurrency group into a Gitea Actions run that is awaiting approval. When a later run in that group cancels the blocked job, the run becomes terminal while still marked as needing… | ||
| 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-2026-123002 | Hig | 0.49 | 7.5 | 0.00 | Nov 15, 2026 | Gitea accepted an unlimited number of wrong TOTP passcodes during sign-in, in the password reset flow and for Basic authentication with the `X-Gitea-OTP` header. An attacker who already knows an account's password could guess the six-digit passcode by trying codes at a high rate… | ||
| CVE-2026-58438 | Hig | 0.49 | 7.5 | 0.00 | Aug 13, 2026 | Cross-repository IDOR in issue-dependency removal lets an attacker tamper with and comment on private repos they cannot access |
- risk 0.52cvss 9.1epss 0.00
Gitea Remember-Me Token Theft Not Invalidating Attacker Session
- risk 0.52cvss 9.1epss 0.01
Gitea versions before 1.25.5 do not persist the OAuth2 PKCE S256 challenge method correctly during authorization, allowing token exchange without the expected verifier check.
- risk 0.52cvss 9.1epss 0.01
Gitea versions before 1.25.5 do not consistently enforce OAuth2 authorization code expiry and single-use behavior during token exchange.
- risk 0.52cvss 9.1epss 0.01
Gitea versions before 1.25.5 mishandle path resolution during template repository generation, allowing template processing to read or write through symlinked or otherwise non-regular paths.
- risk 0.52cvss 9.1epss 0.01
Gitea versions before 1.25.5 lack validation constraints for repository creation fields, including length-limited template fields and trust model or object format values.
- risk 0.52cvss 9.1epss 0.01
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 resolves local reusable workflow files from a fork's head commit when a trusted base-branch workflow runs for a pull_request_target event. A fork author can modify a referenced reusable workflow so attacker-controlled code executes with the repository and organization…
- risk 0.50cvss 8.8epss 0.00
Gitea's OpenID connect handler accepts a user's password without enforcing enrolled TOTP or WebAuthn verification before completing sign-in and linking an OpenID identifier. When OpenID sign-in is enabled, an attacker who knows the victim's password can obtain a session and link…
- risk 0.50cvss 8.8epss 0.00
Gitea's pull request review notifier does not attach the pull request to the Actions notification, so the fork workflow approval gate does not recognize the run as originating from a fork. Review comment and review approval or rejection events can consequently load workflow code…
- risk 0.50cvss 8.8epss 0.00
Gitea Actions blocks the jobs of workflow runs from first-time fork pull request contributors until a maintainer approves the run. The rerun path only required a run to be finished and built the new attempt's jobs without considering the pending approval, so when a user with…
- risk 0.50cvss 8.8epss 0.00
A user who can open a fork pull request can place workflow content with a shared run-level concurrency group into a Gitea Actions run that is awaiting approval. When a later run in that group cancels the blocked job, the run becomes terminal while still marked as needing…
- 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 7.5epss 0.00
Gitea accepted an unlimited number of wrong TOTP passcodes during sign-in, in the password reset flow and for Basic authentication with the `X-Gitea-OTP` header. An attacker who already knows an account's password could guess the six-digit passcode by trying codes at a high rate…
- risk 0.49cvss 7.5epss 0.00
Cross-repository IDOR in issue-dependency removal lets an attacker tamper with and comment on private repos they cannot access
Page 3 of 14