PatchSiren cyber security CVE debrief
CVE-2026-73273 Gitea CVE debrief
An authenticated user with package-publish permission can submit an oversized body to a checksum endpoint in Gitea, bypassing the upload quota. This can lead to potential memory exhaustion and denial of service. Defenders should assess exposure and prioritize verifying Gitea instances with package-publish permissions enabled. The vulnerability allows authenticated users to bypass upload quotas and potentially exhaust server memory, impacting Gitea instances with package-publish permissions enabled.
- Vendor
- Gitea
- Product
- Unknown
- CVSS
- Unknown
- CISA KEV
- Not listed in stored evidence
- Original CVE published
- 2026-10-14
- Original CVE updated
- 2026-10-14
- Advisory published
- 2026-10-14
- Advisory updated
- 2026-10-14
Who should care
Defenders responsible for Gitea instances with package-publish permissions enabled should assess exposure and potential memory exhaustion impact. They should prioritize verifying Gitea instances and review compensating controls for exposed systems. Security teams and vulnerability management teams should also review and limit package-publish permissions for authenticated users.
Why it matters
Defenders should prioritize verifying exposure and assessing potential memory exhaustion impact on Gitea instances with package-publish permissions enabled. This vulnerability allows authenticated users to bypass upload quotas and potentially exhaust server memory.
- Potential memory exhaustion due to oversized checksum uploads
- Upload quota bypass for authenticated users with package-publish permissions
- Possible denial of service due to server memory exhaustion
Technical summary
Gitea's Maven upload handler reads checksum uploads entirely into memory and returns before enforcing package-size quotas. An authenticated user with package-publish permission can submit an oversized body to a checksum endpoint despite legitimate checksum values being at most 128 bytes. This bypasses the upload quota on that path and can exhaust server memory, impacting Gitea instances with package-publish permissions enabled. Defenders should prioritize verifying exposure and assessing potential memory exhaustion impact.
Defensive priority
Defenders should prioritize verifying exposure and assessing potential memory exhaustion impact on Gitea instances with package-publish permissions enabled.
Recommended defensive actions
- Verify Gitea instance exposure and assess potential memory exhaustion impact
- Review and limit package-publish permissions for authenticated users
- Monitor server memory usage and adjust quotas as necessary
- Review compensating controls for exposed systems while remediation is scheduled and verified
- Check relevant monitoring, detection, and logs for exposed assets that need extra review
- Track exceptions, retest remediated assets, and close the item only after evidence is documented
- Confirm whether affected product deployments exist in managed environments and assign an owner for follow-up
Evidence notes
The CVE record and source item provide details on the vulnerability, including its description and affected versions. Defenders should verify Gitea instances with package-publish permissions enabled and assess potential memory exhaustion impact. The vulnerability allows authenticated users to bypass upload quotas and potentially exhaust server memory. Evidence is limited to CVE Program records and source item details.
Sources and references
Verified primary and authoritative sources
-
CVE-2026-73273 CVE Program record
Publisher, destination, and source semantics verified
URL: https://www.cve.org/CVERecord?id=CVE-2026-73273
CVE Program - Official CVE Program record with source-provided CVE metadata.
-
CVE-2026-73273 NVD vulnerability detail
Publisher, destination, and source semantics verified
URL: https://nvd.nist.gov/vuln/detail/CVE-2026-73273
NIST National Vulnerability Database - Official NIST NVD detail page and source-specific vulnerability assessment.
Supplemental references
-
Gitea Maven checksum upload quota bypass and memory exhaustion
Unverified legacy reference
URL: https://raw.githubusercontent.com/CVEProject/cvelistV5/main/cves/2026/73xxx/CVE-2026-73273.json
cve_program_cvelist_v5
-
Source reference
Unverified legacy reference
URL: https://github.com/go-gitea/gitea/security/advisories/GHSA-5xcq-p92v-43rf
Supplemental source - vendor-advisory
-
Source reference
Unverified legacy reference
URL: https://blog.gitea.com/release-of-1.27.3/
Supplemental source - release-notes
-
Source reference
Unverified legacy reference
URL: https://github.com/go-gitea/gitea/pull/39028
Supplemental source - patch
-
Source reference
Unverified legacy reference
URL: https://github.com/go-gitea/gitea/pull/39031
Supplemental source - patch
-
Source reference
Unverified legacy reference
URL: https://github.com/go-gitea/gitea/releases/tag/v1.27.3
Supplemental source - release-notes
Methodology and review provenance
AI-assisted synthesis based on stored public vulnerability evidence. System validation, approval state, and publication status do not by themselves establish human review of this revision. PatchSiren helps prioritize defensive review and does not prove exposure or remediation on any system.