Gitea vulnerabilities

By year

Bars are flaws published each year; the red part is the share attackers have used.

Exploited Gitea flaws

These are on CISA’s Known Exploited Vulnerabilities list, newest first. If you run any of these products, these come before everything else.

• CVE-2026-60004 Gitea Code InjectionExploited since Aug 25, 2026 · CVSS 9.8

Latest high and critical flaws

• CVE-2026-109553 Gitea resolved the principals of an SSH certificate by searching the content of all stored public keys instead of only principal keys.High 7.5 · Oct 18, 2026
• CVE-2026-73804 Gitea allows a token with write:user scope to register an attacker-controlled SSH public key on the token owner's account.High 8.1 · Oct 14, 2026
• CVE-2026-73802 Gitea Runner passes workflow-controlled container options into Docker job container configuration while privileged mode is disabled.High 8.8 · Oct 14, 2026
• CVE-2026-73800 Gitea resolves local reusable workflow files from a fork's head commit when a trusted base-branch workflow runs for a pull_request_target event.High 8.8 · Oct 14, 2026
• CVE-2026-73539 Gitea substitutes a URL derived from the markup Context field into external renderer command templates without escaping the reference path before shell-style arHigh 7.5 · Oct 14, 2026
• CVE-2026-73535 Gitea's OpenID connect handler accepts a user's password without enforcing enrolled TOTP or WebAuthn verification before completing sign-in and linking an OpenIHigh 8.8 · Oct 14, 2026
• CVE-2026-71184 Gitea's pull request review notifier does not attach the pull request to the Actions notification, so the fork workflow approval gate does not recognize the runHigh 8.8 · Oct 14, 2026
• CVE-2026-66877 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.High 8.1 · Oct 14, 2026
• CVE-2026-59774 Gitea's Org-mode markup renderer processes INCLUDE directives supplied to the repository markup endpoint without preventing access to server-side files.Critical 9.8 · Oct 14, 2026
• CVE-2026-86684 The Gitea push mirror API checked whether the repository owner, instead of the requesting user, may use local file system paths.High 7.1 · Oct 6, 2026
• CVE-2026-105267 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 deleHigh 8.1 · Oct 6, 2026
• CVE-2026-101023 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 toCritical 9.1 · Oct 6, 2026
• CVE-2026-96580 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 apprHigh 7.5 · Oct 6, 2026
• CVE-2026-96404 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 iHigh 8.1 · Oct 6, 2026
• CVE-2026-96399 A repository's external issue tracker regular expression containing alternating capture groups could produce invalid slice indexes when Gitea rendered issue refHigh 7.5 · Oct 6, 2026
• CVE-2026-95106 Gitea accepted pushed Git trees containing two entries with the same name, which Git's own consistency checks reject.Critical 9.1 · Oct 6, 2026
• CVE-2026-94205 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.Critical 9.8 · Oct 6, 2026
• CVE-2026-89430 Gitea validated a push mirror's remote address against the `[migrations]` allow and block lists only when the mirror was created.High 8.1 · Oct 6, 2026
• CVE-2026-79960 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 theHigh 7.1 · Oct 6, 2026
• CVE-2026-73278 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.Critical 9.8 · Oct 6, 2026
• CVE-2026-70357 Gitea validates a repository migration hostname against its network allow and block lists before invoking Git, but the Git subprocess independently resolves theHigh 7.5 · Oct 6, 2026
• CVE-2026-104636 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 fHigh 7.5 · Oct 6, 2026
• CVE-2026-104632 Gitea Actions blocks the jobs of workflow runs from first-time fork pull request contributors until a maintainer approves the run.High 8.8 · Oct 6, 2026
• CVE-2026-104626 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.High 8.8 · Oct 6, 2026
• CVE-2026-103670 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 High 7.5 · Oct 6, 2026