Overview 37 matches · 1 in Waratek scope · 0 protected · 0 exploited · 0 CISA KEV · 2 public PoC · 1 EPSS ≥ 0.5
37matches
1in Waratek scope2.7%
0protected0.0%
0exploited0.0%
0CISA KEV0.0%
2public PoC5.4%
1EPSS ≥ 0.52.7%
Protected by Waratek
0
0.0%
Rule in development
0
0.0%
Mitigation candidate
0
0.0%
No exploit published
1
2.7%
Outside Waratek scope
0
0.0%
Not applicable
36
97.3%
Withdrawn CVE
0
0.0%
blocked by ARMR today
0
0.0%
partly blocked
0
0.0%
not blocked
37
100.0%
not established
0
0.0%
unrecorded
0
0.0%
Exploited
0
0.0%
Working exploit published
2
5.4%
Proof of concept only
1
2.7%
Forecast only
0
0.0%
No public exploit
34
91.9%
split by
peak 15 / year
20181
Not applicable1
Medium1
not blocked1
No public exploit1
20193
Not applicable3
Medium3
not blocked3
No public exploit3
20200
20211
Not applicable1
Medium1
not blocked1
No public exploit1
20227
No exploit published1
Not applicable6
Medium7
not blocked7
Working exploit published2
No public exploit5
20232
Not applicable2
Medium2
not blocked2
No public exploit2
20240
20258
Not applicable8
Medium8
not blocked8
No public exploit8
202615
Not applicable15
Medium15
not blocked15
Proof of concept only1
No public exploit14
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-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-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-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-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-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-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-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-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-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-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-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-46685 | Medium | 2022-12-12 | No exploit published | No public exploit | In Jenkins Gitea Plugin 1.4.4 and earlier, the implementation of Gitea personal access tokens did not support credentials masking, potentially exposing them through the build log. |
| 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-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-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-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-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-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-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. |