Gitea
by Go Gitea
Source repositories
CVEs (265)
| CVE | Vendor / Product | Sev | Risk | CVSS | EPSS | KEV | Published | Description |
|---|---|---|---|---|---|---|---|---|
| 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. |
- 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.
Page 4 of 14