CVE-2026-105964 json
Gitea Actions artifact v4 API unbounded request body
published 22d ago modified 21d ago also EUVD-2026-103985
- cvss
- 6.5
- version 3.1, CNA
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 0.3%
- EPSS 0.3% chance of exploitation in 30 days, percentile 23%
- public exploits
- 0
- none known
Summary
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.
Patch / fix
- github.com/go-gitea/gitea#39818 pull request
- github.com/go-gitea/gitea#39822 pull request
- github.com/go-gitea/gitea/releases/tag/v28.2.0 release
Is CVE-2026-105964 in your stack? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.
Check with FencerCISA SSVC
- Exploitation
- none
- Automatable
- no
- Technical impact
- partial
- Assessed
- 21d ago
Exploit prediction
0.31% chance of exploitation in the next 30 days, higher than 23% of all scored CVEs (FIRST EPSS, 2026-11-09).
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| CISA ADP | 3.1 | 6.5 | CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H |
| CNA | 3.1 | 6.5 | CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H |
Affected products
- Gitea Gitea
Classification
- Weakness
-
- CWE-770 Allocation of Resources Without Limits or Throttling
References
-
github.com
/go-gitea/gitea/pull/39818
patch
-
github.com
/go-gitea/gitea/pull/39822
patch
-
github.com
/go-gitea/gitea/security/advisories/GHSA-6f9g-7jgm-m5ph
vendor-advisory
-
blog.gitea.com
/release-of-28.2.0/
release-notes
-
github.com
/go-gitea/gitea/releases/tag/v28.2.0
release-notes
Sources
- CVE List CVE-2026-105964
- NVD CVE-2026-105964
Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.