Vendor CVEs
Go Gitea
All CVEs
265 total · sorted by risk| CVE | Vendor / Product | Sev | Risk | CVSS | EPSS | KEV | Published | Description |
|---|---|---|---|---|---|---|---|---|
| CVE-2026-58427 | Hig | 0.42 | 7.5 | 0.00 | Aug 13, 2026 | Private org member list leaked via /members API endpoint — incomplete fix for PR #38145 | ||
| CVE-2026-58417 | Hig | 0.42 | 7.5 | 0.00 | Aug 13, 2026 | REST API exposes organization membership of private organizations to public | ||
| CVE-2026-42931 | Med | 0.42 | 6.5 | 0.01 | Aug 13, 2026 | Denial of Service via Unbounded io.ReadAll in NPM Package Tag Endpoint | ||
| CVE-2026-34966 | Hig | 0.42 | 7.6 | 0.00 | Aug 5, 2026 | Gitea prior to 1.27.0 contains a server-side request forgery vulnerability that allows authenticated attackers to bypass SSRF protections by exploiting HTTP fetch operations in migration and OAuth avatar code paths that use Go's default http.Get without a custom DialContext.… | ||
| CVE-2026-58421 | Hig | 0.42 | 7.5 | 0.00 | Jul 3, 2026 | Unauthenticated ReDoS via CODEOWNERS pattern matching allows denial of service | ||
| CVE-2026-58419 | Hig | 0.42 | 7.5 | 0.00 | Jul 3, 2026 | Notification API leaks private issue metadata after access revocation | ||
| CVE-2026-27779 | Hig | 0.42 | 7.5 | 0.01 | Jul 3, 2026 | Gitea versions before 1.25.5 accept malformed or injected forwarded-proto values when detecting public URLs, allowing spoofed canonical URL generation. | ||
| CVE-2026-27660 | Hig | 0.42 | 7.5 | 0.00 | Jul 3, 2026 | Gitea versions before 1.25.5 allow draft release data or attachments to be accessed without the required write permission. | ||
| CVE-2026-27657 | Hig | 0.42 | 7.5 | 0.00 | Jul 3, 2026 | Gitea versions before 1.25.5 allow a user to change another user's primary email address. | ||
| CVE-2026-26307 | Hig | 0.42 | 7.5 | 0.01 | Jul 3, 2026 | Gitea versions before 1.25.5 do not enforce a timeout on git grep searches, allowing expensive searches to consume server resources. | ||
| CVE-2026-25712 | Hig | 0.42 | 7.5 | 0.00 | Jul 3, 2026 | Gitea versions before 1.25.5 have insufficient visibility checks in organization permission APIs for hidden members and private organizations. | ||
| CVE-2026-25038 | Hig | 0.42 | 7.5 | 0.01 | Jul 3, 2026 | Gitea 1.26.2 allows unauthorized users to access labels of private organizations. | ||
| CVE-2026-24690 | Hig | 0.42 | 7.5 | 0.00 | Jul 3, 2026 | Gitea versions before 1.25.5 have insufficient permission checks for updating or rebasing pull request branches. | ||
| CVE-2026-24451 | Hig | 0.42 | 7.5 | 0.00 | Jul 3, 2026 | Gitea 1.26.2 allows fork synchronization to continue after a parent repository changes from public to private, exposing data to a fork that should no longer be authorized. | ||
| CVE-2026-20736 | Hig | 0.42 | 7.5 | 0.00 | Jan 22, 2026 | Gitea does not properly verify repository context when deleting attachments. A user who previously uploaded an attachment to a repository may be able to delete it after losing access to that repository by making the request through a different repository they can access. | ||
| CVE-2022-27313 | Hig | 0.42 | 7.5 | 0.01 | May 3, 2022 | An arbitrary file deletion vulnerability in Gitea v1.16.3 allows attackers to cause a Denial of Service (DoS) via deleting the configuration file. | ||
| CVE-2021-39867 | Med | 0.42 | 6.5 | 0.01 | Oct 5, 2021 | In all versions of GitLab CE/EE since version 8.15, a DNS rebinding vulnerability in Gitea Importer may be exploited by an attacker to trigger Server Side Request Forgery (SSRF) attacks. | ||
| CVE-2019-10330 | Hig | 0.42 | 7.5 | 0.02 | May 31, 2019 | Jenkins Gitea Plugin 1.1.1 and earlier did not implement trusted revisions, allowing attackers without commit access to the Git repo to change Jenkinsfiles even if Jenkins is configured to consider them to be untrusted. | ||
| CVE-2019-1000002 | Med | 0.42 | 6.5 | 0.01 | Feb 4, 2019 | Gitea version 1.6.2 and earlier contains a Incorrect Access Control vulnerability in Delete/Edit file functionallity that can result in the attacker deleting files outside the repository he/she has access to. This attack appears to be exploitable via the attacker must get write… | ||
| CVE-2026-58441 | Med | 0.41 | 6.3 | 0.00 | Aug 13, 2026 | SSRF in restore-repo via unsanitized pull_request.yml Head.CloneURL | ||
| CVE-2026-25779 | Med | 0.40 | 6.1 | 0.00 | Jul 3, 2026 | Gitea versions up to and including 1.25.4 allow redirect bypasses through raw or percent-encoded backslashes in redirect_to values. | ||
| CVE-2021-45329 | Med | 0.40 | 6.1 | 0.01 | Feb 8, 2022 | Cross Site Scripting (XSS) vulnerability exists in Gitea before 1.5.1 via the repository settings inside the external wiki/issue tracker URL field. | ||
| CVE-2019-1010261 | Med | 0.40 | 6.1 | 0.01 | Jul 18, 2019 | Gitea 1.7.0 and earlier is affected by: Cross Site Scripting (XSS). The impact is: Attacker is able to have victim execute arbitrary JS in browser. The component is: go-get URL generation - PR to fix: https://github.com/go-gitea/gitea/pull/5905. The attack vector is: victim must… | ||
| CVE-2026-86684 | Hig | 0.39 | 7.1 | 0.00 | Oct 6, 2026 | The Gitea push mirror API checked whether the repository owner, instead of the requesting user, may use local file system paths. On instances with `[security] IMPORT_LOCAL_PATHS = true`, a repository administrator who is not allowed to import local paths could add a push mirror… | ||
| CVE-2026-79960 | Hig | 0.39 | 7.1 | 0.00 | Oct 6, 2026 | When a push was authenticated with a deploy key, Gitea recorded the repository owner as the pusher, so permission checks in the push hook pipeline evaluated the owner instead of the deploy key. A holder of a writable deploy key could create protected tags without being on the… | ||
| CVE-2026-58437 | Hig | 0.39 | 7.1 | 0.00 | Aug 13, 2026 | Repository Visibility Manipulation via Git Push Options | ||
| CVE-2026-58416 | Hig | 0.39 | 7.1 | 0.00 | Aug 13, 2026 | Fork-PR Actions task can read a third private repository via the collaborative-owner branch (missing fork-PR guard) | ||
| CVE-2026-28740 | Hig | 0.39 | 7.1 | 0.00 | Jul 3, 2026 | Gitea versions up to and including 1.26.2 allow Git LFS object reuse to authorize private source objects for users who have repository access but lack Code-unit access. | ||
| CVE-2026-20779 | Hig | 0.39 | 7.1 | 0.00 | Jul 3, 2026 | Gitea versions from 1.5.0 before 1.26.3 have a TOTP single-use enforcement defect that allows a valid TOTP code to be accepted more than once across web two-factor authentication flows and the Basic Auth X-Gitea-OTP path. | ||
| CVE-2022-0905 | Hig | 0.39 | 7.1 | 0.01 | Mar 10, 2022 | Missing Authorization in GitHub repository go-gitea/gitea prior to 1.16.4. | ||
| CVE-2026-123065 | Med | 0.37 | 5.7 | 0.00 | Nov 15, 2026 | When a release was edited, the files of the attachments to remove were deleted by the identifiers submitted in the form rather than by the attachments verified to belong to the release. A user with write access to the releases of any repository, including their own, could submit… | ||
| CVE-2026-58440 | Med | 0.37 | 6.8 | 0.00 | Aug 13, 2026 | Webhooks created by a collaborator keep firing after their repo access is revoked → ongoing real-time exfiltration of private repo content (incomplete revocation cleanup in `DeleteCollaboration`) | ||
| CVE-2022-1058 | Med | 0.37 | 6.1 | 0.53 | Mar 24, 2022 | Open Redirect on login in GitHub repository go-gitea/gitea prior to 1.16.5. | ||
| CVE-2026-118535 | Med | 0.36 | 5.5 | 0.00 | Nov 15, 2026 | A repository registered by its owner as a source of scoped workflows kept that registration when it was transferred to another owner. The new owner could then change the workflows in the transferred repository, and they kept running in the previous owner's repositories with… | ||
| CVE-2026-129525 | Med | 0.35 | 5.4 | 0.00 | Nov 15, 2026 | Several endpoints that work on both issues and pull requests did not check which of the two the addressed item is. A user who can read a repository's issues but not its pull requests could read pull request data through the issue sub-resources of the API (timeline, attachments,… | ||
| CVE-2026-129341 | Med | 0.35 | 5.4 | 0.00 | Nov 15, 2026 | The web endpoint that removes an attachment skipped the permission check when the request came from the user who had uploaded the attachment, and it was reachable with read access to issues or pull requests. A user who had uploaded a release asset could still delete it after… | ||
| CVE-2026-128359 | Med | 0.35 | 5.4 | 0.00 | Nov 15, 2026 | When Gitea acts as an OAuth2 or OpenID Connect provider, the token endpoint did not check the state of the user. After an administrator deactivated an account or prohibited its sign-in, existing refresh tokens and unused authorization codes of that user could still be exchanged… | ||
| CVE-2026-120729 | Med | 0.35 | 5.4 | 0.00 | Nov 15, 2026 | The popup shown when hovering an issue reference loaded its data from the path of the hovered link and inserted part of the response as HTML. A user who can post a comment or other rendered content could add a link that is displayed as an ordinary issue reference but points to a… | ||
| CVE-2026-118504 | Med | 0.35 | 6.5 | 0.00 | Nov 1, 2026 | The web interface blocks issue and pull request changes on archived repositories, but several issue routes of the REST API did not check whether the repository is archived. A user allowed to change issues of an archived repository could use the API to edit, close or delete… | ||
| CVE-2026-118386 | Med | 0.35 | 6.5 | 0.00 | Nov 1, 2026 | Workflows triggered by a pull request review were read from the commit named in the review's `commit_id`, while the fork restrictions were decided by the reviewed pull request, and the commit was not checked to belong to that pull request. A user with read access to a repository… | ||
| CVE-2026-117677 | Med | 0.35 | 6.5 | 0.01 | Nov 1, 2026 | When parsing an uploaded Helm chart, Gitea decompressed the archive and read every tar entry while looking for `Chart.yaml` without limiting the decompressed size, and did so before the package size quota was checked; the quota only considers the compressed upload size. A user… | ||
| CVE-2026-117635 | Med | 0.35 | 6.5 | 0.01 | Nov 1, 2026 | The `/api/v1/admin` route group did not enforce the `public-only` restriction of personal access tokens. A public-only token with admin scope issued by a site administrator could therefore list private organizations and the email addresses of all users, create organizations,… | ||
| CVE-2026-116474 | Med | 0.35 | 6.5 | 0.00 | Nov 1, 2026 | The `GITEA_TOKEN` of a Gitea Actions job authenticates as the `gitea-actions` system user, and the `/api/v1/user` email and GPG key endpoints accepted that user, so a job could register an email address and a GPG key on it; without required email confirmation (the default) the… | ||
| CVE-2026-116296 | Med | 0.35 | 6.5 | 0.00 | Nov 1, 2026 | The API routes for releases, release assets, milestones and repository labels did not reject changes to archived repositories. A user with write access to an archived repository, or a holder of such a user's write-scoped token, could replace or delete release assets while… | ||
| CVE-2026-97859 | Med | 0.35 | 6.5 | 0.00 | Oct 18, 2026 | Seven Gitea API routes under `/api/v1/users/{username}` (followers, following, following/{target}, starred, subscriptions, keys and gpg_keys) were registered without the `individualPermsChecker` middleware that enforces the visibility of the target user. An authenticated user… | ||
| CVE-2026-110324 | Med | 0.35 | 6.5 | 0.00 | Oct 18, 2026 | The visibility check of Gitea user profiles was applied to GET requests only, while `POST /{username}` (follow and unfollow) required only a signed-in user. Any authenticated user could therefore obtain the full name, location, website and description of a user with a private… | ||
| CVE-2026-105964 | Med | 0.35 | 6.5 | 0.00 | Oct 18, 2026 | The Gitea Actions artifact v4 (Twirp) handlers read the whole request body into memory without a size limit. A user who can run a workflow and obtains the runner token of that run could send an oversized request to the artifact service and exhaust the memory of the server, which… | ||
| CVE-2026-73814 | Med | 0.35 | 6.5 | 0.00 | Oct 14, 2026 | Gitea's collaboration access-mode endpoint accepts the Owner access mode from an authenticated repository collaborator with Admin access. The collaborator can promote their effective permissions from Admin to Owner and then perform owner-only operations, including transferring… | ||
| CVE-2026-70406 | Med | 0.35 | 6.5 | 0.00 | Oct 14, 2026 | Gitea's shared comparison helper omits the token repository-access check used when updating pull requests. A public-only token with read:repository scope can route a comparison or pull request creation through a public base repository and retrieve commit history and diffs from a… | ||
| CVE-2026-66874 | Med | 0.35 | 6.5 | 0.00 | Oct 14, 2026 | For pull request events, Gitea reads workflow definitions from the pull request head and posts a synthetic skipped status when workflow branch or path filters exclude execution. A fork pull request author can supply a workflow matching a required status context but deliberately… |
- risk 0.42cvss 7.5epss 0.00
Private org member list leaked via /members API endpoint — incomplete fix for PR #38145
- risk 0.42cvss 7.5epss 0.00
REST API exposes organization membership of private organizations to public
- risk 0.42cvss 6.5epss 0.01
Denial of Service via Unbounded io.ReadAll in NPM Package Tag Endpoint
- risk 0.42cvss 7.6epss 0.00
Gitea prior to 1.27.0 contains a server-side request forgery vulnerability that allows authenticated attackers to bypass SSRF protections by exploiting HTTP fetch operations in migration and OAuth avatar code paths that use Go's default http.Get without a custom DialContext.…
- risk 0.42cvss 7.5epss 0.00
Unauthenticated ReDoS via CODEOWNERS pattern matching allows denial of service
- risk 0.42cvss 7.5epss 0.00
Notification API leaks private issue metadata after access revocation
- risk 0.42cvss 7.5epss 0.01
Gitea versions before 1.25.5 accept malformed or injected forwarded-proto values when detecting public URLs, allowing spoofed canonical URL generation.
- risk 0.42cvss 7.5epss 0.00
Gitea versions before 1.25.5 allow draft release data or attachments to be accessed without the required write permission.
- risk 0.42cvss 7.5epss 0.00
Gitea versions before 1.25.5 allow a user to change another user's primary email address.
- risk 0.42cvss 7.5epss 0.01
Gitea versions before 1.25.5 do not enforce a timeout on git grep searches, allowing expensive searches to consume server resources.
- risk 0.42cvss 7.5epss 0.00
Gitea versions before 1.25.5 have insufficient visibility checks in organization permission APIs for hidden members and private organizations.
- risk 0.42cvss 7.5epss 0.01
Gitea 1.26.2 allows unauthorized users to access labels of private organizations.
- risk 0.42cvss 7.5epss 0.00
Gitea versions before 1.25.5 have insufficient permission checks for updating or rebasing pull request branches.
- risk 0.42cvss 7.5epss 0.00
Gitea 1.26.2 allows fork synchronization to continue after a parent repository changes from public to private, exposing data to a fork that should no longer be authorized.
- risk 0.42cvss 7.5epss 0.00
Gitea does not properly verify repository context when deleting attachments. A user who previously uploaded an attachment to a repository may be able to delete it after losing access to that repository by making the request through a different repository they can access.
- risk 0.42cvss 7.5epss 0.01
An arbitrary file deletion vulnerability in Gitea v1.16.3 allows attackers to cause a Denial of Service (DoS) via deleting the configuration file.
- risk 0.42cvss 6.5epss 0.01
In all versions of GitLab CE/EE since version 8.15, a DNS rebinding vulnerability in Gitea Importer may be exploited by an attacker to trigger Server Side Request Forgery (SSRF) attacks.
- risk 0.42cvss 7.5epss 0.02
Jenkins Gitea Plugin 1.1.1 and earlier did not implement trusted revisions, allowing attackers without commit access to the Git repo to change Jenkinsfiles even if Jenkins is configured to consider them to be untrusted.
- risk 0.42cvss 6.5epss 0.01
Gitea version 1.6.2 and earlier contains a Incorrect Access Control vulnerability in Delete/Edit file functionallity that can result in the attacker deleting files outside the repository he/she has access to. This attack appears to be exploitable via the attacker must get write…
- risk 0.41cvss 6.3epss 0.00
SSRF in restore-repo via unsanitized pull_request.yml Head.CloneURL
- risk 0.40cvss 6.1epss 0.00
Gitea versions up to and including 1.25.4 allow redirect bypasses through raw or percent-encoded backslashes in redirect_to values.
- risk 0.40cvss 6.1epss 0.01
Cross Site Scripting (XSS) vulnerability exists in Gitea before 1.5.1 via the repository settings inside the external wiki/issue tracker URL field.
- risk 0.40cvss 6.1epss 0.01
Gitea 1.7.0 and earlier is affected by: Cross Site Scripting (XSS). The impact is: Attacker is able to have victim execute arbitrary JS in browser. The component is: go-get URL generation - PR to fix: https://github.com/go-gitea/gitea/pull/5905. The attack vector is: victim must…
- risk 0.39cvss 7.1epss 0.00
The Gitea push mirror API checked whether the repository owner, instead of the requesting user, may use local file system paths. On instances with `[security] IMPORT_LOCAL_PATHS = true`, a repository administrator who is not allowed to import local paths could add a push mirror…
- risk 0.39cvss 7.1epss 0.00
When a push was authenticated with a deploy key, Gitea recorded the repository owner as the pusher, so permission checks in the push hook pipeline evaluated the owner instead of the deploy key. A holder of a writable deploy key could create protected tags without being on the…
- risk 0.39cvss 7.1epss 0.00
Repository Visibility Manipulation via Git Push Options
- risk 0.39cvss 7.1epss 0.00
Fork-PR Actions task can read a third private repository via the collaborative-owner branch (missing fork-PR guard)
- risk 0.39cvss 7.1epss 0.00
Gitea versions up to and including 1.26.2 allow Git LFS object reuse to authorize private source objects for users who have repository access but lack Code-unit access.
- risk 0.39cvss 7.1epss 0.00
Gitea versions from 1.5.0 before 1.26.3 have a TOTP single-use enforcement defect that allows a valid TOTP code to be accepted more than once across web two-factor authentication flows and the Basic Auth X-Gitea-OTP path.
- risk 0.39cvss 7.1epss 0.01
Missing Authorization in GitHub repository go-gitea/gitea prior to 1.16.4.
- risk 0.37cvss 5.7epss 0.00
When a release was edited, the files of the attachments to remove were deleted by the identifiers submitted in the form rather than by the attachments verified to belong to the release. A user with write access to the releases of any repository, including their own, could submit…
- risk 0.37cvss 6.8epss 0.00
Webhooks created by a collaborator keep firing after their repo access is revoked → ongoing real-time exfiltration of private repo content (incomplete revocation cleanup in `DeleteCollaboration`)
- risk 0.37cvss 6.1epss 0.53
Open Redirect on login in GitHub repository go-gitea/gitea prior to 1.16.5.
- risk 0.36cvss 5.5epss 0.00
A repository registered by its owner as a source of scoped workflows kept that registration when it was transferred to another owner. The new owner could then change the workflows in the transferred repository, and they kept running in the previous owner's repositories with…
- risk 0.35cvss 5.4epss 0.00
Several endpoints that work on both issues and pull requests did not check which of the two the addressed item is. A user who can read a repository's issues but not its pull requests could read pull request data through the issue sub-resources of the API (timeline, attachments,…
- risk 0.35cvss 5.4epss 0.00
The web endpoint that removes an attachment skipped the permission check when the request came from the user who had uploaded the attachment, and it was reachable with read access to issues or pull requests. A user who had uploaded a release asset could still delete it after…
- risk 0.35cvss 5.4epss 0.00
When Gitea acts as an OAuth2 or OpenID Connect provider, the token endpoint did not check the state of the user. After an administrator deactivated an account or prohibited its sign-in, existing refresh tokens and unused authorization codes of that user could still be exchanged…
- risk 0.35cvss 5.4epss 0.00
The popup shown when hovering an issue reference loaded its data from the path of the hovered link and inserted part of the response as HTML. A user who can post a comment or other rendered content could add a link that is displayed as an ordinary issue reference but points to a…
- risk 0.35cvss 6.5epss 0.00
The web interface blocks issue and pull request changes on archived repositories, but several issue routes of the REST API did not check whether the repository is archived. A user allowed to change issues of an archived repository could use the API to edit, close or delete…
- risk 0.35cvss 6.5epss 0.00
Workflows triggered by a pull request review were read from the commit named in the review's `commit_id`, while the fork restrictions were decided by the reviewed pull request, and the commit was not checked to belong to that pull request. A user with read access to a repository…
- risk 0.35cvss 6.5epss 0.01
When parsing an uploaded Helm chart, Gitea decompressed the archive and read every tar entry while looking for `Chart.yaml` without limiting the decompressed size, and did so before the package size quota was checked; the quota only considers the compressed upload size. A user…
- risk 0.35cvss 6.5epss 0.01
The `/api/v1/admin` route group did not enforce the `public-only` restriction of personal access tokens. A public-only token with admin scope issued by a site administrator could therefore list private organizations and the email addresses of all users, create organizations,…
- risk 0.35cvss 6.5epss 0.00
The `GITEA_TOKEN` of a Gitea Actions job authenticates as the `gitea-actions` system user, and the `/api/v1/user` email and GPG key endpoints accepted that user, so a job could register an email address and a GPG key on it; without required email confirmation (the default) the…
- risk 0.35cvss 6.5epss 0.00
The API routes for releases, release assets, milestones and repository labels did not reject changes to archived repositories. A user with write access to an archived repository, or a holder of such a user's write-scoped token, could replace or delete release assets while…
- risk 0.35cvss 6.5epss 0.00
Seven Gitea API routes under `/api/v1/users/{username}` (followers, following, following/{target}, starred, subscriptions, keys and gpg_keys) were registered without the `individualPermsChecker` middleware that enforces the visibility of the target user. An authenticated user…
- risk 0.35cvss 6.5epss 0.00
The visibility check of Gitea user profiles was applied to GET requests only, while `POST /{username}` (follow and unfollow) required only a signed-in user. Any authenticated user could therefore obtain the full name, location, website and description of a user with a private…
- risk 0.35cvss 6.5epss 0.00
The Gitea Actions artifact v4 (Twirp) handlers read the whole request body into memory without a size limit. A user who can run a workflow and obtains the runner token of that run could send an oversized request to the artifact service and exhaust the memory of the server, which…
- risk 0.35cvss 6.5epss 0.00
Gitea's collaboration access-mode endpoint accepts the Owner access mode from an authenticated repository collaborator with Admin access. The collaborator can promote their effective permissions from Admin to Owner and then perform owner-only operations, including transferring…
- risk 0.35cvss 6.5epss 0.00
Gitea's shared comparison helper omits the token repository-access check used when updating pull requests. A public-only token with read:repository scope can route a comparison or pull request creation through a public base repository and retrieve commit history and diffs from a…
- risk 0.35cvss 6.5epss 0.00
For pull request events, Gitea reads workflow definitions from the pull request head and posts a synthetic skipped status when workflow branch or path filters exclude execution. A fork pull request author can supply a workflow matching a required status context but deliberately…
Page 3 of 6