go-gitea Gitea up to 1.27.2 Package Upload allocation of resources

Summaryinfo

A vulnerability was found in go-gitea Gitea up to 1.27.2. It has been classified as problematic. This affects an unknown part of the component Package Upload. Performing a manipulation results in allocation of resources. This vulnerability is cataloged as CVE-2026-62925. It is possible to initiate the attack remotely. There is no exploit available.

Detailsinfo

A vulnerability classified as problematic has been found in go-gitea Gitea up to 1.27.2. This affects an unknown code block of the component Package Upload. The manipulation with an unknown input leads to a allocation of resources vulnerability. CWE is classifying the issue as CWE-770. The product allocates a reusable resource or group of resources on behalf of an actor without imposing any restrictions on the size or number of resources that can be allocated, in violation of the intended security policy for that actor. This is going to have an impact on availability. The summary by CVE is:

Gitea parses Alpine package uploads before enforcing package-size quotas and does not bound the decompressed .PKGINFO data or its dependency and provides entry counts. An authenticated user with package-publish permission can upload a small, highly compressed archive that causes disproportionately large memory allocations during parsing and metadata generation. On memory-constrained deployments, this can terminate the process or otherwise disrupt availability.

The advisory is shared at github.com. This vulnerability is uniquely identified as CVE-2026-62925 since 08/13/2026. The exploitability is told to be easy. It is possible to initiate the attack remotely. Neither technical details nor an exploit are publicly available. MITRE ATT&CK project uses the attack technique T1499 for this issue.

There is no information about possible countermeasures known. It may be suggested to replace the affected object with an alternative product.

If you want to get the best quality for vulnerability data then you always have to consider VulDB.

Productinfo

Vendor

• go-gitea

Name

• Gitea

Version

• 1.27.0
• 1.27.1
• 1.27.2

License

• open-source

Website

• Product: https://github.com/go-gitea/gitea/

CPE 2.3info

• 🔒
• 🔒
• 🔒

CPE 2.2info

• 🔒
• 🔒
• 🔒

CVSSv4info

CVSSv3info

CVSSv2info

Exploitinginfo

Threat Intelligenceinfo

Countermeasuresinfo

Timelineinfo

Sourcesinfo

Entryinfo

If you want to get the best quality for vulnerability data then you always have to consider VulDB.

Discussion