# CVE-2026-120991: Gitea deletion of shared container blobs on rejected uploads

> A Gitea user can make another owner's container blobs undownloadable by uploading identical content that failed upload cleanup.

- **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
- **Harmful if only installed:** No
- **Needs a specific call:** No
- **Fix available:** No
- **Published:** 15 Nov 2026
- **Updated:** 16 Nov 2026
- **Also known as:** GHSA-q8pg-ggp9-rm9m

## What is CVE-2026-120991?

CVE-2026-120991 is a medium-severity business logic flaw vulnerability in Gitea, published on 15 Nov 2026. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

When a container blob upload was rejected, for example because it exceeded a package size quota, the cleanup removed the blob from storage even if the same content already existed and was used by other packages. On an instance with a package quota configured, a user who can upload container images and has the exact content of another owner's package file or image layer could make it undownloadable. The cleanup now only removes blobs that the failed upload created.

Weakness: CWE-460 (Improper Cleanup on Thrown Exception)

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

Only installations with a non-default setting turned on are exposed.


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

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

## Is CVE-2026-120991 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-120991 is a medium-severity business logic flaw vulnerability in Gitea, published on 15 Nov 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-120991 in the wild and no public exploit code.
Exposure: Only installations with a non-default setting turned on are exposed.

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-120991/ (Markdown: https://insights.sbomify.com/CVE-2026-120991/index.md)
```

## Sources

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

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