Live › vulnerability › CVE-2026-105964
Go to dashboardThe Gitea Actions artifact v4 (Twirp) handlers read the entire request body into memory with no size limit. A user who can run a workflow and holds that run's runner token can send an oversized request and exhaust server memory, crashing the Gitea process.
Summary written from the sources below. Check the originals before acting.
First seen by InfraStack 2026-10-23 21:57 UTC. All times on this page are UTC.
Self-hosted Gitea instances with Gitea Actions enabled are exposed, since the flaw is in the artifact service that runners call. Instances with Actions disabled, or those that run only on hosted Gitea services managed by someone else, can skip it; the sources do not name the affected version range.
No product ranges from the sources yet.
gitea --version or the version shown in the admin dashboard.[actions] ENABLED = true).Each row is the first time that source carried this signal. The analyst’s rows are its own findings.
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 Gitea process. The request body is now limited to 1 MiB.
This page as .md · .json · in your agent: get_signal("CVE-2026-105964")
NVD data is provided by NIST and is public domain. Posts quoted belong to their authors.