Overview 79 matches · 0 in Waratek scope · 0 protected · 1 exploited · 1 CISA KEV · 6 public PoC · 4 EPSS ≥ 0.5
79matches
0in Waratek scope0.0%
0protected0.0%
1exploited1.3%
1CISA KEV1.3%
6public PoC7.6%
4EPSS ≥ 0.55.1%
Protected by Waratek
0
0.0%
Rule in development
0
0.0%
Mitigation candidate
0
0.0%
No exploit published
0
0.0%
Outside Waratek scope
0
0.0%
Not applicable
79
100.0%
Withdrawn CVE
0
0.0%
blocked by ARMR today
0
0.0%
partly blocked
0
0.0%
not blocked
79
100.0%
not established
0
0.0%
unrecorded
0
0.0%
split by
peak 39 / year
20183
Not applicable3
Critical1
High1
Medium1
not blocked3
No public exploit3
20196
Not applicable6
Critical1
High2
Medium3
not blocked6
Working exploit published1
No public exploit5
20203
Not applicable3
Critical1
High2
not blocked3
Working exploit published1
No public exploit2
20212
Not applicable2
High1
Medium1
not blocked2
No public exploit2
202215
Not applicable15
Critical4
High5
Medium6
not blocked15
Working exploit published3
No public exploit12
20232
Not applicable2
Medium2
not blocked2
No public exploit2
20240
20259
Not applicable9
High1
Medium8
not blocked9
No public exploit9
202639
Not applicable39
Critical9
High14
Medium15
Low1
not blocked39
Exploited1
Proof of concept only1
No public exploit37
201820192020202120222023202420252026
| CVE | Severity | Published▾ | Status | Exploitation | Description |
|---|---|---|---|---|---|
| CVE-2026-97208 | Medium | 2026-10-06 | Not applicable | No public exploit | The Gitea API endpoint for creating push mirrors (`POST /api/v1/repos/{owner}/{repo}/push_mirrors`) checked only whether mirroring was enabled and not the `[mirror] DISABLE_NEW_PUSH` setting that the web interface enforces. A repository administrator could therefore create new push mirrors on instances where the site administrator had disabled them. A push mirror pushes all refs of the repository to a remote chosen by the caller, on each commit or on a schedule. |
| CVE-2026-96594 | Medium | 2026-10-06 | Not applicable | No public exploit | The Gitea API endpoint `GET /api/v1/repos/{owner}/{repo}/media/{filepath}` wrote files of up to 1 KiB that are stored directly in Git, not in LFS, to the response without the content type and disposition headers Gitea uses for user content. An HTML file committed to a repository was therefore rendered by the browser on the Gitea origin. A user who can push to a repository could run JavaScript in the session of a victim who opens the media URL and act with the victim's permissions. |
| CVE-2026-96589 | Medium | 2026-10-06 | Not applicable | No public exploit | When a private repository is transferred to a user who lacks access, Gitea grants that recipient temporary read access as a collaborator so they can review the repository. Rejecting or cancelling the transfer did not revoke this collaboration, so the named recipient kept persistent read access to the private repository, including its code, issues, pull requests and wiki, and could clone it. The repository owner was not notified. Transfer-granted access is now removed while collaborations that existed before the transfer are preserved. |
| CVE-2026-96580 | High | 2026-10-06 | Not applicable | No public exploit | 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 expands to a very large number of jobs, consuming server memory and potentially terminating the Gitea process. No runner is required. Static matrices above 256 combinations are now rejected before expansion. |
| CVE-2026-96404 | High | 2026-10-06 | Not applicable | No public exploit | 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 account without verifying its password. If the account is an administrator, the session grants full administrative access, including changing the account's password. Databases with a single user also did not require the reinstall confirmation. |
| CVE-2026-96400 | Medium | 2026-10-06 | Not applicable | No public exploit | With `[migrations] ALLOWED_DOMAINS` set to a matching entry such as `*` or a hostname wildcard, Gitea's migration URL validation could permit reserved and link-local addresses, such as `169.254.169.254`, even when `ALLOW_LOCALNETWORKS = false`. The local-network block list did not cover these ranges, and a hostname matching the allow list was accepted regardless of its resolved address. A user who can start migrations on such an instance could reach these addresses from the Gitea server; the default empty `ALLOWED_DOMAINS` configuration is not affected. |
| CVE-2026-96399 | High | 2026-10-06 | Not applicable | No public exploit | 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 tracker settings could make any later rendering of matching content, such as viewing a README, crash the instance for all users. |
| CVE-2026-95112 | Medium | 2026-10-06 | Not applicable | No public exploit | When processing issue and comment bodies, Gitea scanned the entire preceding text for action keywords such as "closes" or "fixes" once per Markdown link, giving processing time quadratic in the input size. An authenticated user able to submit issue or comment content could send a crafted body of about 1 MB that keeps a CPU core busy for several minutes while holding a database transaction open. |
| CVE-2026-95106 | Critical | 2026-10-06 | Not applicable | No public exploit | Gitea accepted pushed Git trees containing two entries with the same name, which Git's own consistency checks reject. Gitea's web views resolved such a path to the first entry, while `git checkout`, Gitea Actions, and release archives use the last. A contributor could open a pull request whose diff and file views show benign content while CI and checkouts at the same commit use different, attacker-controlled content. Incoming objects are now checked for consistency; objects already stored in existing repositories are not rescanned. |
| CVE-2026-94205 | Critical | 2026-10-06 | Not applicable | No public exploit | 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 requiring approval, while the workflow definition was still taken from the fork head. Where Actions is enabled and a matching runner is registered, fork-controlled workflow code could run on the base repository's runners without an explicit approval. |
| CVE-2026-89430 | High | 2026-10-06 | Not applicable | No public exploit | 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 reached. A user with administrator access to a repository, which includes repositories they create themselves, could aim push mirror synchronization at internal Git services and force-push the repository's contents to them. |
| CVE-2026-89182 | Medium | 2026-10-06 | Not applicable | Proof of concept only | With `[repository] FORCE_PRIVATE = true`, Gitea creates new repositories as private, but the post-receive hook still applied the `repo.private=false` push option to an empty repository created by push. Any user who can create repositories could make their new repository public in violation of the instance policy. The default configuration is not affected. |
| CVE-2026-86684 | High | 2026-10-06 | Not applicable | No public exploit | 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 to a local path on the server when the repository owner has that permission. Gitea then pushed the repository's refs into an existing Git repository at that path with the permissions of the Gitea process. |
| CVE-2026-79960 | High | 2026-10-06 | Not applicable | No public exploit | 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 tag allow list and change repository visibility through push options, for example making a private repository public. Pull requests created through the AGit flow with a deploy key were also attributed to the owner. |
| CVE-2026-73278 | Critical | 2026-10-06 | Not applicable | No public exploit | 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 enforced during password login. One affected path can also persist an external identity link, extending the compromise beyond the initial session; accounts with TOTP configured are outside the reported WebAuthn-only scenario. |
| CVE-2026-70357 | High | 2026-10-06 | Not applicable | No public exploit | 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 address between validation and connection to reach a blocked internal address. The affected path is the Git clone operation; validation in the migration HTTP client's dialer does not protect the independently connecting Git subprocess. |
| CVE-2026-105268 | Medium | 2026-10-06 | Not applicable | No public exploit | The Gitea API routes for issue attachments (`/api/v1/repos/{owner}/{repo}/issues/{index}/assets/{attachment_id}`) also accepted attachments that belong to comments on the issue. Because the author of an issue may edit and delete the issue's attachments, a user who opened an issue could rename or delete attachments that other users had posted in comments on that issue. The contents of the attachments could not be changed. |
| CVE-2026-105267 | High | 2026-10-06 | Not applicable | No public exploit | 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 write access could permanently delete published releases of that repository, including their attachments. Protected tag rules covering the release tag still blocked the deletion. |
| CVE-2026-104636 | High | 2026-10-06 | Not applicable | No public exploit | 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 that redirects could make Gitea's Git client send requests to an address that the outbound host policy would otherwise block. The impact depends on the configured policy and the internal services reachable from the server. |
| CVE-2026-104633 | Medium | 2026-10-06 | Not applicable | No public exploit | When migrating a repository from another Gitea instance, Gitea used the page size reported in the source server's API settings to end its paginated downloads. A source that reported `max_response_items` as `0` made these loops run indefinitely and grow server memory until it was exhausted. Any user who can migrate repositories could point a migration at a server they control and cause a denial of service. |
| CVE-2026-104632 | High | 2026-10-06 | Not applicable | No public exploit | 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 Actions write access cancelled a run that was awaiting approval and then re-ran it, the new jobs were created as waiting rather than blocked while the run still recorded that approval was required. Cancelling and re-running stale fork checks is a routine action that does not involve the approval control, so where Actions is enabled and a matching runner is registered, workflow code taken from the fork pull request head could run on the repository's runners without an explicit approval. |
| CVE-2026-104626 | High | 2026-10-06 | Not applicable | No public exploit | 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 approval. If a maintainer later approves the run, Gitea passed the already-cancelled job back through concurrency preparation, set it to waiting, and made it claimable by a matching runner, executing fork-controlled workflow code. Exploitation requires the maintainer's later approval action, Actions to be enabled, and a runner that accepts the repository's jobs. |
| CVE-2026-103670 | High | 2026-10-06 | Not applicable | No public exploit | 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 from a fork could cancel trusted in-progress runs that share a concurrency group with `cancel-in-progress` enabled, without approval and without running any code. On self-hosted runners this can interrupt deployments and leave partial state behind. |
| CVE-2026-103667 | Medium | 2026-10-06 | Not applicable | No public exploit | Gitea's container registry served blob downloads with a `Content-Type` taken from the media type declared in pushed image manifests, without a `Content-Disposition` or restrictive content security policy. A user who can push container images can publish a blob containing HTML and JavaScript with a `text/html` media type. When a victim who is authenticated to the instance opens the blob URL in a browser, the script runs on the Gitea origin and can perform actions as the victim, such as creating API tokens. |
| CVE-2026-103059 | Critical | 2026-10-06 | Not applicable | No public exploit | When Gitea's built-in SSH server is enabled (`START_SSH_SERVER = true`), the presented public key was looked up with an SQL `LIKE` comparison of its encoded content, which is case-insensitive on some databases, including the default SQLite. An attacker who can construct a case variant of another user's registered RSA public key for which they can derive the private key could have that key matched to the victim's account and authenticate over SSH as that user. Keys are now looked up by fingerprint. |
| CVE-2026-101029 | Medium | 2026-10-06 | Not applicable | No public exploit | Gitea's repository migration and pull mirror egress checks could be bypassed with a hostname that returns multiple DNS answers, because the address that was validated was not necessarily the address Git later connected to. A low-privileged user who can create migrations or mirrors could direct the server to internal services, reading from and writing to reachable internal Git or HTTP endpoints. Content from internal responses could additionally be disclosed through migration and mirror error messages. |
| CVE-2026-101027 | High | 2026-10-06 | Not applicable | No public exploit | 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 resolve to loopback or private addresses and bypass `ALLOW_LOCALNETWORKS = false`, reaching internal services from the Gitea server. Instances without `ALLOWED_DOMAINS` configured are not affected by this specific bypass. |
| CVE-2026-101023 | Critical | 2026-10-06 | Not applicable | No public exploit | Gitea's OAuth2 token endpoint verified the signature and grant of a token submitted with the `refresh_token` grant type, but not that the token was a refresh token. An unexpired access token for the same OAuth2 application and grant could be exchanged for a new access token and refresh token. Whoever holds such an access token could keep access beyond the token's original lifetime. |
| CVE-2026-60004 | Critical | 2026-08-26 | Not applicable | Exploited | Gitea before 1.27.1 allows remote code execution via the diffpatch API through Git hook installation. |
| CVE-2026-20912 | Critical | 2026-01-22 | Not applicable | No public exploit | 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-20904 | Medium | 2026-01-22 | Not applicable | No public exploit | Gitea does not properly validate ownership when toggling OpenID URI visibility. An authenticated user may be able to change the visibility settings of other users' OpenID identities. |
| CVE-2026-20897 | Critical | 2026-01-22 | Not applicable | No public exploit | 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-20888 | Medium | 2026-01-22 | Not applicable | No public exploit | Gitea does not properly verify authorization when canceling scheduled auto-merges via the web interface. A user with read access to pull requests may be able to cancel auto-merges scheduled by other users. |
| CVE-2026-20883 | Medium | 2026-01-22 | Not applicable | No public exploit | Gitea's stopwatch API does not re-validate repository access permissions. After a user's access to a private repository is revoked, they may still view issue titles and repository names through previously started stopwatches. |
| CVE-2026-20800 | Medium | 2026-01-22 | Not applicable | No public exploit | Gitea's notification API does not re-validate repository access permissions when returning notification details. After a user's access to a private repository is revoked, they may still view issue and pull request titles through previously received notifications. |
| CVE-2026-20750 | Critical | 2026-01-22 | Not applicable | No public exploit | 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-2026-20736 | High | 2026-01-22 | Not applicable | No public exploit | 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-2026-0798 | Low | 2026-01-22 | Not applicable | No public exploit | Gitea may send release notification emails for private repositories to users whose access has been revoked. When a repository is changed from public to private, users who previously watched the repository may continue to receive release notifications, potentially disclosing release titles, tags, and content. |
| CVE-2025-69413 | Medium | 2026-01-01 | Not applicable | No public exploit | In Gitea before 1.25.2, /api/v1/user has different responses for failed authentication depending on whether a username exists. |
| CVE-2025-68946 | Medium | 2025-12-26 | Not applicable | No public exploit | In Gitea before 1.20.1, a forbidden URL scheme such as javascript: can be used for a link, aka XSS. |
| CVE-2025-68945 | Medium | 2025-12-26 | Not applicable | No public exploit | In Gitea before 1.21.2, an anonymous user can visit a private user's project. |
| CVE-2025-68944 | Medium | 2025-12-26 | Not applicable | No public exploit | Gitea before 1.22.2 sometimes mishandles the propagation of token scope for access control within one of its own package registries. |
| CVE-2025-68943 | Medium | 2025-12-26 | Not applicable | No public exploit | Gitea before 1.21.8 inadvertently discloses users' login times by allowing (for example) the lastlogintime explore/users sort order. |
| CVE-2025-68942 | Medium | 2025-12-26 | Not applicable | No public exploit | Gitea before 1.22.2 allows XSS because the search input box (for creating tags and branches) is v-html instead of v-text. |
| CVE-2025-68941 | Medium | 2025-12-26 | Not applicable | No public exploit | Gitea before 1.22.3 mishandles access to a private resource upon receiving an API token with scope limited to public resources. |
| CVE-2025-68940 | Medium | 2025-12-26 | Not applicable | No public exploit | In Gitea before 1.22.5, branch deletion permissions are not adequately enforced after merging a pull request. |
| CVE-2025-68939 | High | 2025-12-26 | Not applicable | No public exploit | Gitea before 1.23.0 allows attackers to add attachments with forbidden file extensions by editing an attachment name via an attachment API. |
| CVE-2025-68938 | Medium | 2025-12-26 | Not applicable | No public exploit | Gitea before 1.25.2 mishandles authorization for deletion of releases. |
| CVE-2022-38795 | Medium | 2023-08-07 | Not applicable | No public exploit | In Gitea through 1.17.1, repo cloning can occur in the migration function. |
| CVE-2023-3515 | Medium | 2023-07-05 | Not applicable | No public exploit | Open Redirect in GitHub repository go-gitea/gitea prior to 1.19.4. |
| CVE-2022-42968 | Critical | 2022-10-16 | Not applicable | No public exploit | Gitea before 1.17.3 does not sanitize and escape refs in the git backend. Arguments to git commands are mishandled. |
| CVE-2022-38183 | Medium | 2022-08-12 | Not applicable | No public exploit | In Gitea before 1.16.9, it was possible for users to add existing issues to projects. Due to improper access controls, an attacker could assign any issue to any project in Gitea (there was no permission check for fetching the issue). As a result, the attacker would get access to private issue titles. |
| CVE-2022-1928 | Medium | 2022-05-29 | Not applicable | No public exploit | Cross-site Scripting (XSS) - Stored in GitHub repository go-gitea/gitea prior to 1.16.9. |
| CVE-2022-30781 | High | 2022-05-16 | Not applicable | Working exploit published | Gitea before 1.16.7 does not escape git fetch remote. |
| CVE-2022-27313 | High | 2022-05-03 | Not applicable | No public exploit | 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-2022-1058 | Medium | 2022-03-24 | Not applicable | Working exploit published | Open Redirect on login in GitHub repository go-gitea/gitea prior to 1.16.5. |
| CVE-2021-29134 | Medium | 2022-03-15 | Not applicable | No public exploit | The avatar middleware in Gitea before 1.13.6 allows Directory Traversal via a crafted URL. |
| CVE-2022-0905 | High | 2022-03-10 | Not applicable | No public exploit | Missing Authorization in GitHub repository go-gitea/gitea prior to 1.16.4. |
| CVE-2021-45331 | Critical | 2022-02-09 | Not applicable | No public exploit | 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 | Critical | 2022-02-09 | Not applicable | No public exploit | 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-2021-45329 | Medium | 2022-02-08 | Not applicable | No public exploit | 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-2021-45328 | Medium | 2022-02-08 | Not applicable | Working exploit published | Gitea before 1.4.3 is affected by URL Redirection to Untrusted Site ('Open Redirect') via internal URLs. |
| CVE-2021-45327 | Critical | 2022-02-08 | Not applicable | No public exploit | Gitea before 1.11.2 is affected by Trusting HTTP Permission Methods on the Server Side when referencing the vulnerable admin or user API. which could let a remote malisious user execute arbitrary code. |
| CVE-2021-45326 | High | 2022-02-08 | Not applicable | No public exploit | Cross Site Request Forgery (CSRF) vulnerability exists in Gitea before 1.5.2 via API routes.This can be dangerous especially with state altering POST requests. |
| CVE-2021-45325 | High | 2022-02-08 | Not applicable | No public exploit | Server Side Request Forgery (SSRF) vulneraility exists in Gitea before 1.7.0 using the OpenID URL. |
| CVE-2021-28378 | Medium | 2021-03-15 | Not applicable | No public exploit | Gitea 1.12.x and 1.13.x before 1.13.4 allows XSS via certain issue data in some situations. |
| CVE-2021-3382 | High | 2021-02-05 | Not applicable | No public exploit | 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-28991 | Critical | 2020-11-24 | Not applicable | No public exploit | 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-2020-14144 | High | 2020-10-16 | Not applicable | Working exploit published | 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 ENABLE_GIT_HOOKS line in the config file). NOTE: The vendor has indicated this is not a vulnerability and states "This is a functionality of the software that is limited to a very limited subset of accounts. If you give someone the privilege to execute arbitrary code on your server, they can execute arbitrary code on your server. We provide very clear warnings to users around this functionality and what it provides. |
| CVE-2020-13246 | High | 2020-05-20 | Not applicable | No public exploit | 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-1010261 | Medium | 2019-07-18 | Not applicable | No public exploit | 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 open a specifically crafted URL. The fixed version is: 1.7.1 and later. |
| CVE-2019-1010314 | Medium | 2019-07-11 | Not applicable | No public exploit | Gitea 1.7.2, 1.7.3 is affected by: Cross Site Scripting (XSS). The impact is: execute JavaScript in victim's browser, when the vulnerable repo page is loaded. The component is: repository's description. The attack vector is: victim must navigate to public and affected repo page. |
| CVE-2019-11576 | Critical | 2019-04-28 | Not applicable | No public exploit | 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-2019-11229 | High | 2019-04-15 | Not applicable | Working exploit published | 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-2019-11228 | High | 2019-04-15 | Not applicable | No public exploit | 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-2019-1000002 | Medium | 2019-02-04 | Not applicable | No public exploit | 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 access to "any" repository including self-created ones.. This vulnerability appears to have been fixed in 1.6.3, 1.7.0-rc2. |
| CVE-2018-18926 | Critical | 2018-11-04 | Not applicable | No public exploit | Gitea before 1.5.4 allows remote code execution because it does not properly validate session IDs. This is related to session ID handling in the go-macaron/session code for Macaron. |
| CVE-2018-1000803 | Medium | 2018-10-08 | Not applicable | No public exploit | Gitea version prior to version 1.5.1 contains a CWE-200 vulnerability that can result in Exposure of users private email addresses. This attack appear to be exploitable via Watch a repository to receive email notifications. Emails received contain the other recipients even if they have the email set as private. This vulnerability appears to have been fixed in 1.5.1. |
| CVE-2018-15192 | High | 2018-08-08 | Not applicable | No public exploit | 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. |