Vendor CVEs
Go Gitea
All CVEs
265 total · sorted by risk| CVE | Vendor / Product | Sev | Risk | CVSS | EPSS | KEV | Published | Description |
|---|---|---|---|---|---|---|---|---|
| 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 | ||
| CVE-2026-54481 | Hig | 0.49 | 7.5 | 0.00 | Aug 13, 2026 | Internal API HTTP client hardcodes InsecureSkipVerify:true with no config override (CWE-295) | ||
| CVE-2021-45325 | Hig | 0.49 | 7.5 | 0.01 | Feb 8, 2022 | Server Side Request Forgery (SSRF) vulneraility exists in Gitea before 1.7.0 using the OpenID URL. | ||
| CVE-2021-3382 | Hig | 0.49 | 7.5 | 0.02 | Feb 5, 2021 | Stack buffer overflow vulnerability in gitea 1.9.0 through 1.13.1 allows remote attackers to cause a denial of service (crash) via vectors related to a file path. | ||
| CVE-2020-13246 | Hig | 0.49 | 7.5 | 0.02 | May 20, 2020 | An issue was discovered in Gitea through 1.11.5. An attacker can trigger a deadlock by initiating a transfer of a repository's ownership from one organization to another. | ||
| CVE-2019-11228 | Hig | 0.49 | 7.5 | 0.01 | Apr 15, 2019 | repo/setting.go in Gitea before 1.7.6 and 1.8.x before 1.8-RC3 does not validate the form.MirrorAddress before calling SaveAddress. | ||
| 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-107618 | Hig | 0.46 | 8.1 | 0.00 | Oct 18, 2026 | `POST /{owner}/{repo}/topics` was registered without the sign-in middleware that provides the cross-origin protection, so a request issued by a third-party site was not rejected. A repository administrator who visited a malicious page could have the topics of their repository… | ||
| CVE-2026-73804 | Hig | 0.46 | 8.1 | 0.00 | Oct 14, 2026 | Gitea allows a token with write:user scope to register an attacker-controlled SSH public key on the token owner's account. API requests signed with the corresponding private key authenticate as that account through HTTP Signature without API token scope information, causing… | ||
| CVE-2026-66877 | Hig | 0.46 | 8.1 | 0.00 | Oct 14, 2026 | Gitea enforces first-time fork contributor approval by blocking jobs, but some job transition and dispatch paths do not re-check the run's approval requirement. A separate run sharing a job-level concurrency group can cancel a pending job and cause its blocked sibling jobs to be… | ||
| CVE-2026-105267 | Hig | 0.46 | 8.1 | 0.00 | Oct 6, 2026 | The Gitea web route for deleting tags (`POST /{owner}/{repo}/tags/delete`) requires only write access to the Code unit, but shares its handler with release deletion and did not check that the target was a plain tag. A collaborator with Code write access and without Releases… | ||
| CVE-2026-96404 | Hig | 0.46 | 8.1 | 0.01 | Oct 6, 2026 | When Gitea's web installer is reachable against a database that already contains users, such as after `INSTALL_LOCK` has been reset to `false`, submitting the install form with an administrator username matching an existing account issued an authenticated session for that… | ||
| CVE-2026-89430 | Hig | 0.46 | 8.1 | 0.00 | Oct 6, 2026 | Gitea validated a push mirror's remote address against the `[migrations]` allow and block lists only when the mirror was created. Each synchronization passed the stored address directly to `git push`, so a name that later resolved to a blocked or internal address was still… | ||
| CVE-2026-103504 | Hig | 0.46 | 8.1 | 0.00 | Oct 6, 2026 | Changing an organization team's permission through the API with only the `permission` field did not rebuild the team's per-unit access, and the requested level was not applied as a cap. After an organization owner demoted a team, for example from admin to read, the team's… | ||
| CVE-2026-58439 | Hig | 0.46 | 8.1 | 0.01 | Aug 13, 2026 | Branch Protection Bypass via PR Retargeting Preserves Stale `official` Approval Flag | ||
| CVE-2026-24791 | Hig | 0.46 | 8.1 | 0.00 | Aug 13, 2026 | Public-only tokens bypass private-resource restrictions on `/api/v1/user` self routes | ||
| CVE-2026-28744 | Hig | 0.46 | 8.1 | 0.00 | Jul 3, 2026 | Gitea versions up to and including 1.26.1 allow Git smart HTTP requests authenticated with bearer tokens to bypass repository token scope checks. | ||
| CVE-2026-28699 | Hig | 0.46 | 8.1 | 0.01 | Jul 3, 2026 | Gitea versions up to and including 1.26.1 allow OAuth2 access token scope enforcement to be bypassed through HTTP Basic authentication. | ||
| CVE-2026-27771 | Hig | 0.46 | 8.2 | 0.01 | Jul 3, 2026 | Gitea versions up to and including 1.26.1 have insufficient permission checks for Composer package source links, which can expose private or internal package source information. | ||
| CVE-2026-22555 | Hig | 0.46 | 8.1 | 0.00 | Jul 3, 2026 | Gitea versions before 1.26.0 allow API users to fork a repository into an organization without first passing the CanCreateOrgRepo check, which can expose organization secrets. | ||
| CVE-2025-68939 | Hig | 0.46 | 8.2 | 0.00 | Dec 26, 2025 | Gitea before 1.23.0 allows attackers to add attachments with forbidden file extensions by editing an attachment name via an attachment API. | ||
| CVE-2026-101027 | Hig | 0.43 | 7.7 | 0.00 | Oct 6, 2026 | When `[migrations] ALLOWED_DOMAINS` was configured, a hostname matching the allow list was accepted without checking its resolved address against the local-network restrictions. A user who can start repository migrations and control the DNS of an allowed hostname could make it… | ||
| CVE-2026-58314 | Hig | 0.43 | 7.7 | 0.00 | Aug 13, 2026 | Two SSRF findings in Gitea 1.26.2 | ||
| CVE-2026-58423 | Hig | 0.43 | 7.7 | 0.00 | Jul 3, 2026 | LFS authentication bypass via malformed SSH sub-verb allows unauthorized read access to private repositories | ||
| CVE-2026-120991 | Med | 0.42 | 6.5 | 0.00 | Nov 15, 2026 | When a container blob upload was rejected, for example because it exceeded a package size quota, the cleanup removed the blob from storage even if the same content already existed and was used by other packages. On an instance with a package quota configured, a user who can… | ||
| CVE-2026-123006 | Med | 0.42 | 6.5 | 0.00 | Nov 15, 2026 | The repository search used by the dashboard (`GET /repo/search`) returned the internal commit status object of each repository. Since 28.0.0 that object included the repository owner's full user record, so any signed-in user could read the password hash, salt and email address… | ||
| CVE-2026-119533 | Hig | 0.42 | 7.5 | 0.00 | Nov 1, 2026 | Repository and organization project boards listed the pull requests that reference each issue on the board without checking whether the viewer can read them. When a private pull request mentions an issue on a board the viewer can open, the board revealed the private repository's… | ||
| CVE-2026-119441 | Hig | 0.42 | 7.5 | 0.00 | Nov 1, 2026 | `DELETE /api/v1/orgs/{org}/repos` deletes all repositories of an organization, but it did not enforce the public-only restriction of access tokens: the route only checked that the organization itself was public. A public-only token of an owner of a public organization could… | ||
| CVE-2026-118395 | Hig | 0.42 | 7.5 | 0.00 | Nov 1, 2026 | Gitea 1.27.3 stopped personal access tokens restricted to public resources (`public-only`) from creating repositories through `POST /api/v1/user/repos` and `POST /api/v1/repos/migrate`, but `POST /api/v1/org/{org}/repos`, `POST /api/v1/orgs/{org}/repos`, `POST /api/v1/orgs` and… | ||
| CVE-2026-109553 | Hig | 0.42 | 7.5 | 0.00 | Oct 18, 2026 | Gitea resolved the principals of an SSH certificate by searching the content of all stored public keys instead of only principal keys. When Gitea trusts a user certificate authority (`SSH_TRUSTED_USER_CA_KEYS`) and accepts arbitrary principals… | ||
| CVE-2026-73539 | Hig | 0.42 | 7.5 | 0.00 | Oct 14, 2026 | Gitea substitutes a URL derived from the markup Context field into external renderer command templates without escaping the reference path before shell-style argument splitting. A crafted Context can inject additional renderer arguments, including options that load executable… | ||
| CVE-2026-96580 | Hig | 0.42 | 7.5 | 0.00 | Oct 6, 2026 | Gitea expanded a workflow's static `strategy.matrix` into its full Cartesian product without a size limit when creating a run, before the fork pull request approval gate applied. A user who can open a pull request from a fork could submit a small workflow file whose matrix… | ||
| CVE-2026-96399 | Hig | 0.42 | 7.5 | 0.00 | Oct 6, 2026 | A repository's external issue tracker regular expression containing alternating capture groups could produce invalid slice indexes when Gitea rendered issue references, causing a runtime panic that terminated the Gitea process. A user who can edit a repository's external issue… | ||
| CVE-2026-70357 | Hig | 0.42 | 7.5 | 0.00 | Oct 6, 2026 | Gitea validates a repository migration hostname against its network allow and block lists before invoking Git, but the Git subprocess independently resolves the hostname when connecting. An attacker who can start a migration and control the destination's DNS can change the… | ||
| CVE-2026-104636 | Hig | 0.42 | 7.5 | 0.00 | Oct 6, 2026 | Gitea validated the initial remote URL for push mirrors, wiki remote checks, and fetches of migrated pull request heads, but the subsequent raw Git operations followed HTTP redirects without revalidating the destination. A repository administrator using a policy-allowed endpoint… | ||
| CVE-2026-103670 | Hig | 0.42 | 7.5 | 0.00 | Oct 6, 2026 | When a Gitea Actions run was inserted, older runs in the same workflow-level concurrency group were cancelled without checking whether the new run still needed approval. Because fork pull request runs are inserted under the base repository, a user who can open a pull request… | ||
| CVE-2026-59765 | Hig | 0.42 | 7.5 | 0.00 | Aug 13, 2026 | SSRF via Migration Asset Downloads Bypasses hostmatcher — Reads Internal Files and Cloud Metadata | ||
| CVE-2026-58442 | Med | 0.42 | 6.5 | 0.00 | Aug 13, 2026 | Repository migration SSRF via multi-answer DNS allow-list bypass | ||
| CVE-2026-58436 | Hig | 0.42 | 7.5 | 0.01 | Aug 13, 2026 | ParseAcceptLanguage quadratic-time DoS via Locale middleware on unauthenticated requests | ||
| CVE-2026-58434 | Hig | 0.42 | 7.5 | 0.00 | Aug 13, 2026 | Private Repository Metadata Remains Accessible After Access Revocation |
- 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
- risk 0.49cvss 7.5epss 0.00
Internal API HTTP client hardcodes InsecureSkipVerify:true with no config override (CWE-295)
- risk 0.49cvss 7.5epss 0.01
Server Side Request Forgery (SSRF) vulneraility exists in Gitea before 1.7.0 using the OpenID URL.
- risk 0.49cvss 7.5epss 0.02
Stack buffer overflow vulnerability in gitea 1.9.0 through 1.13.1 allows remote attackers to cause a denial of service (crash) via vectors related to a file path.
- risk 0.49cvss 7.5epss 0.02
An issue was discovered in Gitea through 1.11.5. An attacker can trigger a deadlock by initiating a transfer of a repository's ownership from one organization to another.
- risk 0.49cvss 7.5epss 0.01
repo/setting.go in Gitea before 1.7.6 and 1.8.x before 1.8-RC3 does not validate the form.MirrorAddress before calling SaveAddress.
- 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 0.00
`POST /{owner}/{repo}/topics` was registered without the sign-in middleware that provides the cross-origin protection, so a request issued by a third-party site was not rejected. A repository administrator who visited a malicious page could have the topics of their repository…
- risk 0.46cvss 8.1epss 0.00
Gitea allows a token with write:user scope to register an attacker-controlled SSH public key on the token owner's account. API requests signed with the corresponding private key authenticate as that account through HTTP Signature without API token scope information, causing…
- risk 0.46cvss 8.1epss 0.00
Gitea enforces first-time fork contributor approval by blocking jobs, but some job transition and dispatch paths do not re-check the run's approval requirement. A separate run sharing a job-level concurrency group can cancel a pending job and cause its blocked sibling jobs to be…
- risk 0.46cvss 8.1epss 0.00
The Gitea web route for deleting tags (`POST /{owner}/{repo}/tags/delete`) requires only write access to the Code unit, but shares its handler with release deletion and did not check that the target was a plain tag. A collaborator with Code write access and without Releases…
- risk 0.46cvss 8.1epss 0.01
When Gitea's web installer is reachable against a database that already contains users, such as after `INSTALL_LOCK` has been reset to `false`, submitting the install form with an administrator username matching an existing account issued an authenticated session for that…
- risk 0.46cvss 8.1epss 0.00
Gitea validated a push mirror's remote address against the `[migrations]` allow and block lists only when the mirror was created. Each synchronization passed the stored address directly to `git push`, so a name that later resolved to a blocked or internal address was still…
- risk 0.46cvss 8.1epss 0.00
Changing an organization team's permission through the API with only the `permission` field did not rebuild the team's per-unit access, and the requested level was not applied as a cap. After an organization owner demoted a team, for example from admin to read, the team's…
- risk 0.46cvss 8.1epss 0.01
Branch Protection Bypass via PR Retargeting Preserves Stale `official` Approval Flag
- risk 0.46cvss 8.1epss 0.00
Public-only tokens bypass private-resource restrictions on `/api/v1/user` self routes
- risk 0.46cvss 8.1epss 0.00
Gitea versions up to and including 1.26.1 allow Git smart HTTP requests authenticated with bearer tokens to bypass repository token scope checks.
- risk 0.46cvss 8.1epss 0.01
Gitea versions up to and including 1.26.1 allow OAuth2 access token scope enforcement to be bypassed through HTTP Basic authentication.
- risk 0.46cvss 8.2epss 0.01
Gitea versions up to and including 1.26.1 have insufficient permission checks for Composer package source links, which can expose private or internal package source information.
- risk 0.46cvss 8.1epss 0.00
Gitea versions before 1.26.0 allow API users to fork a repository into an organization without first passing the CanCreateOrgRepo check, which can expose organization secrets.
- risk 0.46cvss 8.2epss 0.00
Gitea before 1.23.0 allows attackers to add attachments with forbidden file extensions by editing an attachment name via an attachment API.
- risk 0.43cvss 7.7epss 0.00
When `[migrations] ALLOWED_DOMAINS` was configured, a hostname matching the allow list was accepted without checking its resolved address against the local-network restrictions. A user who can start repository migrations and control the DNS of an allowed hostname could make it…
- risk 0.43cvss 7.7epss 0.00
Two SSRF findings in Gitea 1.26.2
- risk 0.43cvss 7.7epss 0.00
LFS authentication bypass via malformed SSH sub-verb allows unauthorized read access to private repositories
- risk 0.42cvss 6.5epss 0.00
When a container blob upload was rejected, for example because it exceeded a package size quota, the cleanup removed the blob from storage even if the same content already existed and was used by other packages. On an instance with a package quota configured, a user who can…
- risk 0.42cvss 6.5epss 0.00
The repository search used by the dashboard (`GET /repo/search`) returned the internal commit status object of each repository. Since 28.0.0 that object included the repository owner's full user record, so any signed-in user could read the password hash, salt and email address…
- risk 0.42cvss 7.5epss 0.00
Repository and organization project boards listed the pull requests that reference each issue on the board without checking whether the viewer can read them. When a private pull request mentions an issue on a board the viewer can open, the board revealed the private repository's…
- risk 0.42cvss 7.5epss 0.00
`DELETE /api/v1/orgs/{org}/repos` deletes all repositories of an organization, but it did not enforce the public-only restriction of access tokens: the route only checked that the organization itself was public. A public-only token of an owner of a public organization could…
- risk 0.42cvss 7.5epss 0.00
Gitea 1.27.3 stopped personal access tokens restricted to public resources (`public-only`) from creating repositories through `POST /api/v1/user/repos` and `POST /api/v1/repos/migrate`, but `POST /api/v1/org/{org}/repos`, `POST /api/v1/orgs/{org}/repos`, `POST /api/v1/orgs` and…
- risk 0.42cvss 7.5epss 0.00
Gitea resolved the principals of an SSH certificate by searching the content of all stored public keys instead of only principal keys. When Gitea trusts a user certificate authority (`SSH_TRUSTED_USER_CA_KEYS`) and accepts arbitrary principals…
- risk 0.42cvss 7.5epss 0.00
Gitea substitutes a URL derived from the markup Context field into external renderer command templates without escaping the reference path before shell-style argument splitting. A crafted Context can inject additional renderer arguments, including options that load executable…
- risk 0.42cvss 7.5epss 0.00
Gitea expanded a workflow's static `strategy.matrix` into its full Cartesian product without a size limit when creating a run, before the fork pull request approval gate applied. A user who can open a pull request from a fork could submit a small workflow file whose matrix…
- risk 0.42cvss 7.5epss 0.00
A repository's external issue tracker regular expression containing alternating capture groups could produce invalid slice indexes when Gitea rendered issue references, causing a runtime panic that terminated the Gitea process. A user who can edit a repository's external issue…
- risk 0.42cvss 7.5epss 0.00
Gitea validates a repository migration hostname against its network allow and block lists before invoking Git, but the Git subprocess independently resolves the hostname when connecting. An attacker who can start a migration and control the destination's DNS can change the…
- risk 0.42cvss 7.5epss 0.00
Gitea validated the initial remote URL for push mirrors, wiki remote checks, and fetches of migrated pull request heads, but the subsequent raw Git operations followed HTTP redirects without revalidating the destination. A repository administrator using a policy-allowed endpoint…
- risk 0.42cvss 7.5epss 0.00
When a Gitea Actions run was inserted, older runs in the same workflow-level concurrency group were cancelled without checking whether the new run still needed approval. Because fork pull request runs are inserted under the base repository, a user who can open a pull request…
- risk 0.42cvss 7.5epss 0.00
SSRF via Migration Asset Downloads Bypasses hostmatcher — Reads Internal Files and Cloud Metadata
- risk 0.42cvss 6.5epss 0.00
Repository migration SSRF via multi-answer DNS allow-list bypass
- risk 0.42cvss 7.5epss 0.01
ParseAcceptLanguage quadratic-time DoS via Locale middleware on unauthenticated requests
- risk 0.42cvss 7.5epss 0.00
Private Repository Metadata Remains Accessible After Access Revocation
Page 2 of 6