CVE-2026-117685

Gitea public-only package token access to private OCI blobs

Published Nov 1, 2026 CVSS 3.1 · 9.1 Critical EPSS < 1% KEV · Not listed
Description
The OCI registry's cross-repository blob mount checked the target package against the token's `public-only` restriction, but checked the source blob only against the full account permissions of the token owner. A `public-only` token with `write:package` scope, whose owner can read a private package and write to a public package namespace, could mount a blob of the private package into the public package. The private blob, such as a container layer, could then be downloaded by anyone through the public package.

Analysis

AI-generated

Technical impact

A flaw in the OCI registry’s cross‑repository blob mount logic allowed a token that is supposed to grant only public package write access to also mount a private blob from a package accessible to the token owner. After mounting, the private blob becomes retrievable by anyone who can download the public package, exposing potentially sensitive container layers. This is an authorization bypass (CWE‑863), leading to confidential data leakage.

Affected Systems

Gitea installations that have not yet applied version 28.3.0. Users running Gitea v28.2.x or earlier are potentially impacted; the advisory indicates that upgrading to v28.3.0 resolves the issue.

Risk and Exploitability

The vulnerability requires a public‑only token with the write:package scope and an owner who also has read permission on a private package. An attacker who can obtain or create such a token can perform a blob mount and thereafter anyone can download the private content via the public repository. The CVSS score of 9.1 indicates a high severity, while the EPSS score of <1% suggests low likelihood of exploitation, yet listing in CISA KEV is absent and does not preclude a potential breach once prerequisites are met.

Remediation

No solution or workaround provided in the CVE record.

OpenCVE Recommended Actions

  • Upgrade Gitea to version 28.3.0 or later to receive the fix that correctly enforces token restrictions on source blobs.
  • Restrict the use of public‑only tokens that have write:package scope; consider revoking this scope for tokens that can also read private packages.
  • If upgrading is not immediately possible, disable public‑only token creation or block cross‑repository blob mounts for public packages until a patch can be applied.

Generated by OpenCVE AI on November 6, 2026 at 17:45 UTC.

Tracking

Sign in to view the affected projects.

Advisories

No advisories available
History
Type Values Removed Values Added
Metrics ssvc

{'options': {'Automatable': 'yes', 'Exploitation': 'none', 'Technical Impact': 'total'}, 'version': '2.0.3'}

Type Values Removed Values Added
Metrics cvssV3_1

{'score': 9.1, 'vector': 'CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:N'}

Type Values Removed Values Added
First Time appeared Gitea
Gitea gitea
Vendors & Products Gitea
Gitea gitea
Type Values Removed Values Added
Description The OCI registry's cross-repository blob mount checked the target package against the token's `public-only` restriction, but checked the source blob only against the full account permissions of the token owner. A `public-only` token with `write:package` scope, whose owner can read a private package and write to a public package namespace, could mount a blob of the private package into the public package. The private blob, such as a container layer, could then be downloaded by anyone through the public package.
Title Gitea public-only package token access to private OCI blobs
Weaknesses CWE-863
References
Weaknesses

Sources

Status
PUBLISHED
Assigner
Gitea
Published
Updated
Nov 6, 2026, 3:25 PM
Reserved
Nov 1, 2026, 8:48 AM
Status
Deferred
Published
Nov 1, 2026, 10:18 AM
Modified
Nov 6, 2026, 4:17 PM