CVE-2026-104633

Gitea migration memory exhaustion from zero page size

Published Oct 6, 2026 CVSS 3.1 · 6.5 Medium EPSS < 1% KEV · Not listed
Description
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.

Analysis

AI-generated

Technical impact

The vulnerability arises when Gitea performs repository migrations and relies on the source server's reported max_response_items to bound paginated downloads. If the source reports a value of zero, the pagination loop continues forever, consuming memory until the server runs out. This results in a denial of service that can affect all users of the instance. The weakness corresponds to resource exhaustion and infinite loop, and attackers that can initiate migrations can target a server they control to trigger the exploit.

Affected Systems

Vendors: Gitea; Product: Gitea. All versions prior to the 28.1.0 release are vulnerable, as the fix was introduced in that version.

Risk and Exploitability

The CVSS score of 6.5 indicates a moderate severity DoS flaw that can be triggered by any user with migration privileges. The EPSS score of less than 1% suggests a low but nonzero likelihood that attackers will attempt to exploit this vulnerability. Because the issue is not listed in the CISA KEV catalog, it is currently considered unpublicly exploited, but the lack of a safeguard on max_response_items means exploitation can occur if a malicious source server reports zero. The attack can be performed by initiating a migration against a controlled server, causing memory exhaustion and downtime for the target instance.

Remediation

No solution or workaround provided in the CVE record.

OpenCVE Recommended Actions

  • Upgrade Gitea to version 28.1.0 or later.
  • Validate source API responses and reject any migration where max_response_items equals zero or is otherwise invalid.
  • Restrict migration functionality to trusted users and repositories, or disable it if not needed.

Generated by OpenCVE AI on October 7, 2026 at 17:23 UTC.

Tracking

Sign in to view the affected projects.

Advisories

No advisories available
History
Type Values Removed Values Added
CPEs cpe:2.3:a:gitea:gitea:*:*:*:*:*:*:*:*
Type Values Removed Values Added
Metrics ssvc

{'options': {'Automatable': 'no', 'Exploitation': 'none', 'Technical Impact': 'partial'}, 'version': '2.0.3'}

Type Values Removed Values Added
Metrics cvssV3_1

{'score': 6.5, 'vector': 'CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H'}

Type Values Removed Values Added
First Time appeared Gitea
Gitea gitea
Vendors & Products Gitea
Gitea gitea
Type Values Removed Values Added
Description 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.
Title Gitea migration memory exhaustion from zero page size
Weaknesses CWE-400
CWE-835
References
Weaknesses
  • CWE-400

    Uncontrolled Resource Consumption

  • CWE-835

    Loop with Unreachable Exit Condition ('Infinite Loop')

Sources

Status
PUBLISHED
Assigner
Gitea
Published
Updated
Oct 7, 2026, 3:53 PM
Reserved
Oct 4, 2026, 10:02 PM
Status
Analyzed
Published
Oct 6, 2026, 10:17 PM
Modified
Oct 13, 2026, 2:38 PM
Severity
Moderate
Public date
Oct 6, 2026, 9:35 PM