Connect your agent
AdvisoriesCriticalCheck your lockfilePluginHow it worksPricing Connect your agent

Advisory record · GHSA-9mq6-mqjj-c2c5

Gitea: Unbounded Arch package file metadata can cause resource amplification in Gitea package uploads

CVSS 4.3 MediumEPSS 0.0029 · 21st percentile

Published by the GitHub Advisory Database at 21 Jul 2026, 20:20 UTC. agentprime has not analysed this yet, so whether it affects any app is not known.

PackageEcosystemAffectedFixed in
code.gitea.io/giteaGo<1.27.01.27.0
Identifiers
GHSA-9mq6-mqjj-c2c5 · CVE-2026-59763 · GO-2026-6049
Weakness (CWE)
CWE-284 · CWE-770
Tags
Published
21 Jul 2026
Updated
22 Jul 2026

Machine-written summary

Summary written by Claude Haiku from the source advisory. Not reviewed by a person.

Gitea versions before 1.27.0 are affected. When an Arch package is uploaded, Gitea records every regular file entry in the archive as package metadata without limiting how many entries or how long their combined names can be. An authenticated user with permission to publish Arch packages can upload a small, highly compressed archive containing a very large number of empty file entries, which inflates server-side parsing, database storage, and repository index generation. Upgrade to Gitea 1.27.0 or later. The source lists no other workaround.

Written 6 Nov 2026.

Not analysed yet

We haven’t published our analysis of this Advisory yet. Once a person has reviewed it, this page will say what’s vulnerable, what has to be true for your app to be affected, and how to check.

Severity and exploitation

ScoreRatingCVSSVectorSource
4.3 Medium 3.1 CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:L ADP (CISA-ADP)
  • CISA KEV Not listed.
  • EPSS 0.0029, the 21st percentile, on 15 Nov 2026: FIRST’s estimate of the chance of exploitation in the next 30 days.

Timeline

  1. 31 Oct 2026, 14:57 UTC First seen by agentprime
  2. 31 Oct 2026, 14:57 UTC Confirmed by OSV

Sources

Facts on this page come from the GitHub Advisory Database (CC-BY 4.0), OSV and the other sources listed, as published. We don’t reproduce full advisory descriptions, which can contain exploit code.