Gitea migration memory exhaustion from zero page size
When migrating a repository from another Gitea instance, Gitea used the page size reported in the source server's API settings to end its paginated downloads. A source that reported `max_response_items` as `0` made these loops run indefinitely and grow server memory until it was exhausted. Any user who can migrate repositories could point a migration at a server they control and cause a denial of service.
01
describes (1)
Related CVEs.
| ID | severity | exploitable | ||
|---|---|---|---|---|
| CVE-2026-104633US | — | — | ||
When migrating a repository from another Gitea instance, Gitea used the page size reported in the source server's API settings to end its paginated downloads. A source that reporte… | ||||
02
references
External citations — patches, advisories, analysis.
- https://blog.gitea.com/release-of-28.1.0/ARTICLE
- https://github.com/go-gitea/gitea/pull/39501FIX
- https://github.com/go-gitea/gitea/pull/39507FIX
- https://github.com/go-gitea/gitea/releases/tag/v28.1.0ARTICLE
- https://github.com/go-gitea/gitea/security/advisories/GHSA-jj5r-9rpc-8h6hADVISORY
- https://nvd.nist.gov/vuln/detail/CVE-2026-104633WEB
scry
Advisories like this name the exposed products attackers go after on your perimeter. See what is exposed on your perimeter with a free passive scan.
Free scan