Gitea Patches Unauthenticated Container Image Disclosure Flaw in 1.26.2

Maintainers of the self-hosted Git platform Gitea have issued a fix for a vulnerability that permitted unauthenticated remote attackers to pull private container images from affected instances without supplying an account, password, or token. The flaw, tracked as CVE-2026-27771, affects all releases prior to Gitea 1.26.2 and was disclosed this week alongside the patched build.

The issue sits in the platform's container registry authorisation path. Gitea bundles an OCI-compatible registry that is supposed to enforce repository visibility on pull operations. In versions before 1.26.2, that check was not consistently applied to manifest and blob requests, which meant a remote party who knew or guessed an organisation and image name could retrieve layers that the owner had marked private.

The practical exposure is meaningful. Container images frequently embed proprietary source, build artefacts, hard-coded secrets, internal certificates, and infrastructure configuration. An anonymous reader who recovers a layer is reading whatever the developer placed in it.

Gitea has not assigned a CVSS score at time of writing. The advisory does not list active exploitation.

Self-hosted forge platforms have drawn sustained attention from researchers over the past eighteen months, with comparable disclosures previously affecting GitLab and Gogs. The pattern is familiar: registry and package endpoints inherit a separate authorisation layer from the main web application, and the seams between the two are where access-control regressions tend to appear.

Administrators running Gitea on-premises should upgrade to 1.26.2 without waiting for a maintenance window where exposure permits. Where an immediate upgrade is not feasible, operators can restrict network access to the /v2/ registry path at the reverse proxy, or temporarily disable the packages feature in app.ini under the [packages] section. Teams that have published sensitive material to private images on internet-facing Gitea servers should treat those secrets as potentially read and rotate them.

There is no public proof-of-concept yet. But the change set is in the open, and reconstructing the bug from a diff is not difficult.

Gitea's release notes for 1.26.2 list the registry authorisation fix alongside several unrelated bug corrections. The maintainers have not indicated whether a backport to the 1.25.x branch is planned; organisations pinned to that line should request clarification through the project's issue tracker. Downstream packagers, including the official container images on Docker Hub, were updated in step with the source release.

Operators with audit logging enabled should review pull events on private repositories going back to the deployment date of any pre-1.26.2 build. Quiet reads do not always leave a trace.