PT-2026-107290

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...

PT-2026-107291

Name of the Vulnerable Software and Affected Versions Gitea affected versions not specified Description The OAuth2 token endpoint fails to verify if a token submitted with the refresh token grant type is actually a refresh token. This allows an unexpired access token for the same OAuth2 applicati...

PT-2026-107175

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...

PT-2026-107176

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...

PT-2026-107169

Name of the Vulnerable Software and Affected Versions Gitea affected versions not specified Description When the built-in SSH server is enabled via the START SSH SERVER variable, the system performs a lookup of the presented public key using an SQL LIKE comparison of its encoded content. Because...

PT-2026-107177

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...

PT-2026-107187

Name of the Vulnerable Software and Affected Versions Gitea affected versions not specified Description The OAuth2 and OpenID Connect sign-in paths fail to require a WebAuthn challenge when WebAuthn is the only configured second factor for an account. This allows an attacker who can authenticate...

PT-2026-107217

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...

PT-2026-107294

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...

PT-2026-107172

Name of the Vulnerable Software and Affected Versions Gitea affected versions not specified Description A flaw exists in Gitea Actions where older runs within the same workflow-level concurrency group are cancelled upon the insertion of a new run without verifying if the new run requires approval...

PT-2026-107293

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...

PT-2026-107221

Name of the Vulnerable Software and Affected Versions Gitea affected versions not specified Description Gitea accepted pushed Git trees containing two entries with the same name, a condition that Git's own consistency checks typically reject. This discrepancy causes Gitea's web views to resolve t...

PT-2026-107218

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...

PT-2026-107292

Name of the Vulnerable Software and Affected Versions Gitea affected versions not specified Description During repository migration from another Gitea instance, the software uses the page size reported by the source server's API to manage paginated downloads. If a source server reports the max...

PT-2026-107186

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...

PT-2026-107223

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...

PT-2026-107129

Name of the Vulnerable Software and Affected Versions Gitea affected versions not specified Description A flaw exists when the migrations ALLOWED DOMAINS configuration is active. The system accepts hostnames matching the allow list without verifying if the resolved address violates local-network...

PT-2026-107289

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...

PT-2026-107224

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...

PT-2026-107226

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...