CVE search
Every published CVE plus open-source advisories (NVD, OSV, GitHub), with CVSS, EPSS and whether it is being exploited in the wild (CISA KEV). Updated every few hours. Our scans match these against the technologies they detect.
Every published CVE plus open-source advisories (NVD, OSV, GitHub), with CVSS, EPSS and whether it is being exploited in the wild (CISA KEV). Updated every few hours. Our scans match these against the technologies they detect.
| 06/10/2026 |
| CVE-2026-103670 | ÉLEVÉE7.5 | 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 | 06/10/2026 |
| CVE-2026-103667 | MOYENNE5.4 | 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 typ | 06/10/2026 |
| CVE-2026-103059 | CRITIQUE9.1 | 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 p | 06/10/2026 |
| CVE-2026-101029 | MOYENNE4.3 | 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 se | 06/10/2026 |
| CVE-2026-101027 | ÉLEVÉE7.7 | 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 a | 06/10/2026 |
| CVE-2026-60004KEV | CRITIQUE9.8 | Gitea before 1.27.1 allows remote code execution via the diffpatch API through Git hook installation. | 26/08/2026 |
| CVE-2026-20912 | CRITIQUE9.1 | 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. | 22/01/2026 |
| CVE-2026-20904 | MOYENNE6.5 | 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. | 22/01/2026 |
| CVE-2026-20897 | CRITIQUE9.1 | 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. | 22/01/2026 |
| CVE-2026-20888 | MOYENNE4.3 | 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. | 22/01/2026 |
| CVE-2026-20883 | MOYENNE6.5 | 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. | 22/01/2026 |
| CVE-2026-20800 | MOYENNE6.5 | 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. | 22/01/2026 |
| CVE-2026-20750 | CRITIQUE9.1 | 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. | 22/01/2026 |
| CVE-2026-20736 | ÉLEVÉE7.5 | 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. | 22/01/2026 |
| CVE-2026-0798 | FAIBLE3.5 | 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. | 22/01/2026 |
| CVE-2025-69413 | MOYENNE5.3 | In Gitea before 1.25.2, /api/v1/user has different responses for failed authentication depending on whether a username exists. | 01/01/2026 |
| CVE-2025-68946 | MOYENNE5.4 | In Gitea before 1.20.1, a forbidden URL scheme such as javascript: can be used for a link, aka XSS. | 26/12/2025 |