# CVE-2026-63021: Gitea Swift package manifest memory exhaustion

> An authenticated user can cause memory exhaustion and service termination in Gitea by uploading a highly compressed archive with many Swift package manifests.

- **Severity:** Medium 6.5 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 14 Oct 2026
- **Updated:** 14 Oct 2026
- **Also known as:** GHSA-fqxf-w92m-prvq

## What is CVE-2026-63021?

CVE-2026-63021 is a medium-severity denial of service vulnerability in Gitea, published on 14 Oct 2026. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

Gitea's Swift package parser limits each manifest to 128 KiB but does not limit the number of manifests or their aggregate size before reading them into memory. An authenticated user with package-publish permission can upload a highly compressed archive containing many manifests, causing allocations far larger than the uploaded archive. This can exhaust memory, terminate the process, or cause request failures.

Weakness: CWE-400 (Uncontrolled Resource Consumption)

## Which versions are affected by CVE-2026-63021?


## How do I fix CVE-2026-63021?

No fix has been published for CVE-2026-63021 yet. Limit exposure of the affected software until one is available.

## Is CVE-2026-63021 being exploited?

There is no known exploitation of CVE-2026-63021 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-63021 and fix it if it is affected.

What it is: CVE-2026-63021 is a medium-severity denial of service vulnerability in Gitea, published on 14 Oct 2026. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-63021 in the wild and no public exploit code.

Affected product: Gitea. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-63021/ (Markdown: https://insights.sbomify.com/CVE-2026-63021/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-63021
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-63021
- OSV: https://osv.dev/vulnerability/CVE-2026-63021

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-63021/
Summaries are generated and may contain mistakes; the official description above is the record.