CVE-2026-120991

Gitea deletion of shared container blobs on rejected uploads

Published Nov 15, 2026 CVSS n/a EPSS n/a KEV · Not listed
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.

Analysis

AI-generated

Technical impact

The vulnerability allows a user who can upload container images on a Gitea instance to delete shared storage blobs by provoking a cleanup routine during a rejected upload. When a container blob upload is rejected—e.g., because the package size exceeds a configured quota—the cleanup logic deletes the blob from storage even if the same content already belongs to other users’ packages. This flaw stems from a failure to isolate the cleanup of failed uploads from legitimate shared blobs (CWE‑460). As a result, affected packages can become permanently unavailable for download.

Affected Systems

Any Gitea installation that has container image upload enabled and enforces a package size quota is potentially affected. The CVE data does not explicitly list the vulnerable versions, but review of linked references indicates that the issue was addressed in the Gitea 28.4.0 release, which is therefore inferred to contain the fix. Administrators should verify whether their current version predates this release and whether upload restrictions are in place.

Risk and Exploitability

The risk is primarily a denial‐of‐service to dependent packages. An attacker only needs authenticated upload privileges and knowledge of a shared blob’s content; no elevated or administrative rights are required. The EPSS score is not published and the vulnerability is not listed in KEV, implying no known public exploits. Nonetheless, the impact on package availability and the potential to disrupt CI/CD pipelines make the threat moderate to high in environments that rely on shared container layers.

Remediation

No solution or workaround provided in the CVE record.

OpenCVE Recommended Actions

  • Upgrade Gitea to version 28.4.0 or later, which contains the fix that limits cleanup to blobs created by the failed upload.
  • Restrict container image upload permissions so that only trusted or minimally privileged users can upload when a package quota is enforced.
  • As a temporary measure, disable the container image upload feature or remove the package size quota until the patch is applied.

Generated by OpenCVE AI on November 15, 2026 at 22:52 UTC.

Tracking

Sign in to view the affected projects.

Advisories

No advisories available
History
Type Values Removed Values Added
First Time appeared Gitea
Gitea gitea
Vendors & Products Gitea
Gitea gitea
Type Values Removed Values Added
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.
Title Gitea deletion of shared container blobs on rejected uploads
Weaknesses CWE-460
References
Weaknesses
  • CWE-460

    Improper Cleanup on Thrown Exception

Sources

Status
PUBLISHED
Assigner
Gitea
Published
Updated
Nov 15, 2026, 9:13 PM
Reserved
Nov 15, 2026, 8:31 PM
Status
Deferred
Published
Nov 15, 2026, 10:17 PM
Modified
Nov 15, 2026, 10:17 PM