Gitea
by Go Gitea
Source repositories
CVEs (265)
| CVE | Vendor / Product | Sev | Risk | CVSS | EPSS | KEV | Published | Description |
|---|---|---|---|---|---|---|---|---|
| CVE-2026-60004 | Cri | 0.71 | 9.8 | 0.24 | KEV | Aug 26, 2026 | Gitea before 1.27.1 allows remote code execution via the diffpatch API through Git hook installation. | |
| CVE-2019-11229 | Hig | 0.65 | 8.8 | 0.55 | Apr 15, 2019 | models/repo_mirror.go in Gitea before 1.7.6 and 1.8.x before 1.8-RC3 mishandles mirror repo URL settings, leading to remote code execution. | ||
| CVE-2021-45331 | Cri | 0.64 | 9.8 | 0.01 | Feb 9, 2022 | 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. | ||
| CVE-2021-45330 | Cri | 0.64 | 9.8 | 0.01 | Feb 9, 2022 | An issue exsits in Gitea through 1.15.7, which could let a malicious user gain privileges due to client side cookies not being deleted and the session remains valid on the server side for reuse. | ||
| CVE-2020-28991 | Cri | 0.64 | 9.8 | 0.02 | Nov 24, 2020 | Gitea 0.9.99 through 1.12.x before 1.12.6 does not prevent a git protocol path that specifies a TCP port number and also contains newlines (with URL encoding) in ParseRemoteAddr in modules/auth/repo_form.go. | ||
| CVE-2019-11576 | Cri | 0.64 | 9.8 | 0.02 | Apr 28, 2019 | Gitea before 1.8.0 allows 1FA for user accounts that have completed 2FA enrollment. If a user's credentials are known, then an attacker could send them to the API without requiring the 2FA one-time password. | ||
| CVE-2025-68937 | Cri | 0.62 | — | 0.01 | 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-59774 | Cri | 0.60 | 9.8 | 0.28 | Oct 14, 2026 | Gitea's Org-mode markup renderer processes INCLUDE directives supplied to the repository markup endpoint without preventing access to server-side files. An unauthenticated attacker can use a suitable public repository to read files accessible to the Gitea service account. If the… | ||
| CVE-2026-58508 | Cri | 0.59 | 9.1 | 0.00 | Aug 13, 2026 | Two SSRF vulnerabilities in Gitea migration/mirror (DNS rebinding + missing re-validation) | ||
| CVE-2026-58443 | Cri | 0.59 | 9.1 | 0.01 | Aug 13, 2026 | Public-only repository tokens can update private PR head branches | ||
| CVE-2026-58433 | Cri | 0.59 | 9.1 | 0.01 | Aug 13, 2026 | Team-repository linking endpoint bypasses the RepoAdminChangeTeamAccess organization setting | ||
| CVE-2026-55982 | Cri | 0.59 | 9.1 | 0.01 | Aug 13, 2026 | OIDC userinfo Endpoint Returns Identity Claims Without Enforcing API Token Scopes | ||
| CVE-2026-118389 | Hig | 0.57 | 8.8 | 0.00 | Nov 15, 2026 | The RubyGems package registry accepted gems whose platform, dependency names or dependency version requirements contain newline characters. Because the compact index served to clients is line-based, a user who can publish a gem to an owner's registry could forge index entries,… | ||
| CVE-2026-125423 | Hig | 0.57 | 8.8 | 0.00 | Nov 15, 2026 | A repository created with auto-init accepted pushes before its initialization had finished, and the initial commit was built in a checkout of whatever the repository already contained. A user who is allowed to create repositories could push a crafted tree during that window so… | ||
| CVE-2026-120263 | Cri | 0.57 | 9.8 | 0.00 | Nov 1, 2026 | When `[oauth2_client].ACCOUNT_LINKING` is set to `auto` (not the default) and registration is enabled, the link-account sign-up form looked up the existing account to link by the user name or email submitted in the form instead of the identity asserted by the OAuth2 provider. An… | ||
| CVE-2026-73802 | Hig | 0.57 | 8.8 | 0.01 | Oct 14, 2026 | Gitea Runner passes workflow-controlled container options into Docker job container configuration while privileged mode is disabled. Host namespace settings, expanded capabilities, and security profile overrides can remain effective despite Privileged being forced false. A… | ||
| CVE-2026-94205 | Cri | 0.57 | 9.8 | 0.01 | Oct 6, 2026 | Gitea Actions decided whether a fork pull request run needed approval based on the user who triggered the event rather than the pull request author. For `pull_request` activity triggered by a maintainer during ordinary triage, such as adding a label, the run was created without… | ||
| CVE-2026-73278 | Cri | 0.57 | 9.8 | 0.00 | Oct 6, 2026 | Gitea's OAuth2 and OpenID Connect sign-in paths do not require a WebAuthn challenge when WebAuthn is the account's only configured second factor. A party able to authenticate through the affected external identity flow can obtain a full session without the passkey verification… | ||
| CVE-2026-56654 | Cri | 0.57 | 9.8 | 0.01 | Aug 13, 2026 | Privilege Escalation via Access Token Scope Escalation in API |
- risk 0.71cvss 9.8epss 0.24
Gitea before 1.27.1 allows remote code execution via the diffpatch API through Git hook installation.
- risk 0.65cvss 8.8epss 0.55
models/repo_mirror.go in Gitea before 1.7.6 and 1.8.x before 1.8-RC3 mishandles mirror repo URL settings, leading to remote code execution.
- risk 0.64cvss 9.8epss 0.01
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.
- risk 0.64cvss 9.8epss 0.01
An issue exsits in Gitea through 1.15.7, which could let a malicious user gain privileges due to client side cookies not being deleted and the session remains valid on the server side for reuse.
- risk 0.64cvss 9.8epss 0.02
Gitea 0.9.99 through 1.12.x before 1.12.6 does not prevent a git protocol path that specifies a TCP port number and also contains newlines (with URL encoding) in ParseRemoteAddr in modules/auth/repo_form.go.
- risk 0.64cvss 9.8epss 0.02
Gitea before 1.8.0 allows 1FA for user accounts that have completed 2FA enrollment. If a user's credentials are known, then an attacker could send them to the API without requiring the 2FA one-time password.
- risk 0.62cvss —epss 0.01
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.60cvss 9.8epss 0.28
Gitea's Org-mode markup renderer processes INCLUDE directives supplied to the repository markup endpoint without preventing access to server-side files. An unauthenticated attacker can use a suitable public repository to read files accessible to the Gitea service account. If the…
- risk 0.59cvss 9.1epss 0.00
Two SSRF vulnerabilities in Gitea migration/mirror (DNS rebinding + missing re-validation)
- risk 0.59cvss 9.1epss 0.01
Public-only repository tokens can update private PR head branches
- risk 0.59cvss 9.1epss 0.01
Team-repository linking endpoint bypasses the RepoAdminChangeTeamAccess organization setting
- risk 0.59cvss 9.1epss 0.01
OIDC userinfo Endpoint Returns Identity Claims Without Enforcing API Token Scopes
- risk 0.57cvss 8.8epss 0.00
The RubyGems package registry accepted gems whose platform, dependency names or dependency version requirements contain newline characters. Because the compact index served to clients is line-based, a user who can publish a gem to an owner's registry could forge index entries,…
- risk 0.57cvss 8.8epss 0.00
A repository created with auto-init accepted pushes before its initialization had finished, and the initial commit was built in a checkout of whatever the repository already contained. A user who is allowed to create repositories could push a crafted tree during that window so…
- risk 0.57cvss 9.8epss 0.00
When `[oauth2_client].ACCOUNT_LINKING` is set to `auto` (not the default) and registration is enabled, the link-account sign-up form looked up the existing account to link by the user name or email submitted in the form instead of the identity asserted by the OAuth2 provider. An…
- risk 0.57cvss 8.8epss 0.01
Gitea Runner passes workflow-controlled container options into Docker job container configuration while privileged mode is disabled. Host namespace settings, expanded capabilities, and security profile overrides can remain effective despite Privileged being forced false. A…
- risk 0.57cvss 9.8epss 0.01
Gitea Actions decided whether a fork pull request run needed approval based on the user who triggered the event rather than the pull request author. For `pull_request` activity triggered by a maintainer during ordinary triage, such as adding a label, the run was created without…
- risk 0.57cvss 9.8epss 0.00
Gitea's OAuth2 and OpenID Connect sign-in paths do not require a WebAuthn challenge when WebAuthn is the account's only configured second factor. A party able to authenticate through the affected external identity flow can obtain a full session without the passkey verification…
- risk 0.57cvss 9.8epss 0.01
Privilege Escalation via Access Token Scope Escalation in API
Page 1 of 14