Vulnerability in Gitea

[ Description ]Official description

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 runs that share a concurrency group with `cancel-in-progress` enabled, without approval and without running any code. On self-hosted runners this can interrupt deployments and leave partial state behind.

[ Fixes ]Fixes and patches

• Patch on github.comVendor patch or bulletin · NVD · Reference tagged 'Patch' by NVD

[ Advisories ]Government CERT advisories

• BSI CERT-Bund6 Oct 2026WID-SEC-2026-3792

  Gitea: Multiple vulnerabilities Translated from German

  CVE-2026-103670CVE-2026-94205CVE-2026-103059+26 more CVEs

[ References ]References

• blog.gitea.com/release-of-28.0.0Release Notes
• github.com/go-gitea/gitea/pull/39399Patch
• github.com/go-gitea/gitea/releases/tag/v28.0.0Release Notes
• github.com/go-gitea/gitea/security/advisories/GHSA-4j4g-m7mr-hp5jVendor Advisory