CVE-2026-104626

A flaw was found in Gitea Actions. An authenticated user capable of submitting a pull request from a repository fork can exploit this vulnerability to execute untrusted workflow code on repository runners. When a workflow job awaiting approval is canceled by a subsequent run within the same...

CVE-2026-105964

The Gitea Actions artifact v4 Twirp handlers read the whole request body into memory without a size limit. A user who can run a workflow and obtains the runner token of that run could send an oversized request to the artifact service and exhaust the memory of the server, which terminates the Gite...

CVE-2026-105964

The Gitea Actions artifact v4 (Twirp) handlers are vulnerable to memory exhaustion because they read the entire request body into memory without an enforced size limit. An attacker who can execute a workflow and obtain a runner token can send an oversized request to the artifact service, exhausti...

CVE-2026-105964 Gitea Actions artifact v4 API unbounded request body

The Gitea Actions artifact v4 Twirp handlers read the whole request body into memory without a size limit. A user who can run a workflow and obtains the runner token of that run could send an oversized request to the artifact service and exhaust the memory of the server, which terminates the Gite...

CVE-2026-105964 Gitea Actions artifact v4 API unbounded request body

The Gitea Actions artifact v4 Twirp handlers read the whole request body into memory without a size limit. A user who can run a workflow and obtains the runner token of that run could send an oversized request to the artifact service and exhaust the memory of the server, which terminates the Gite...

CVE-2026-105964: Allocation of Resources Without Limits or Throttling

The Gitea Actions artifact v4 Twirp handlers read the whole request body into memory without a size limit. A user who can run a workflow and obtains the runner token of that run could send an oversized request to the artifact service and exhaust the memory of the server, which terminates the Gite...

PT-2026-115849

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

CVE-2026-94205

A flaw was found in Gitea Actions. When determining whether workflow runs from fork pull requests require approval, Gitea evaluated the identity of the user triggering the event rather than the author of the pull request. Consequently, routine repository maintainer actions, such as adding a label...

CVE-2026-95106

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

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. For pullrequest activity triggered by a maintainer during ordinary triage, such as adding a label, the run was created without requiring approval,...

CVE-2026-104632

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

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. When a later run in that group cancels the blocked job, the run becomes terminal while still marked as needing approval. If a maintainer...

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 approval. Because fork pull request runs are inserted under the base repository, a user who can open a pull request from a fork could...

CVE-2026-96580 Gitea Actions memory exhaustion through large static matrices

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

CVE-2026-96580 Gitea Actions memory exhaustion through large static matrices

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

CVE-2026-96580 Gitea Actions memory exhaustion through large static matrices

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

CVE-2026-96580

The Gitea Actions service is vulnerable to memory exhaustion because it expands a workflow's static strategy.matrix into a full Cartesian product without a size limit during run creation. This occurs before the fork pull request approval gate is applied, allowing a user with permission to open a ...

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. For "pullrequest" activity triggered by a maintainer during ordinary triage, such as adding a label, the run was created without requiring approval,...

CVE-2026-94205 Gitea fork workflow approval bypass through maintainer-triggered events

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 pullrequest activity triggered by a maintainer during ordinary triage, such as adding a label, the run was created without requiring approval,...

EUVD-2026-93919

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 pullrequest activity triggered by a maintainer during ordinary triage, such as adding a label, the run was created without requiring approval,...