Gitea CVE-2026-27771 exposed private container images without authentication
A vulnerability identified as CVE-2026-27771 allowed unauthenticated access to private container images on Gitea instances for nearly four years. Over 30,000 deployments were affected, raising concerns about the exposure of sensitive information. Users are urged to update to the latest version or implement a temporary configuration change to mitigate the risk.
- ▪CVE-2026-27771 exposed private container images on Gitea instances without authentication.
- ▪The flaw went undetected for four years and affected over 30,000 deployments.
- ▪Users are advised to update to Gitea v1.26.2 or set a temporary configuration to protect their images.
Hacker News (Newest) files mainly under programming. We currently carry 5,306 of its stories.
Story provenance
Source · retrieval · rights · ranking — open for full record
inspect →
Story provenance
Attribution is not the same as permission. This drawer separates discovery metadata, excerpts, WeSearch-generated summaries, reuse status, and whether the publisher receives the visit. Nothing here claims a legal grant the publisher has not made.
Record
| Original publisher | NoScope |
| Canonical URL | https://www.noscope.com/blog/gitea-instances-exposing-private-container |
| Publication time | Fri, 29 May 2026 00:43:12 +0000 |
| Retrieval time | 2026-05-29T00:59:38.922Z |
| Last seen | 2026-05-29T00:59:38.922Z |
| Headline source | Publisher (no WeSearch rewrite) |
| Excerpt source | publisher body |
| Excerpt method | First ~120 words (~800 chars) of extracted publisher body, fair-use limited. |
| Summary | WeSearch · cerebras-chat (WeSearch summarizer) |
| Summary source text | contentText |
| Citation coverage | Summary is a WeSearch-generated derivative; primary citation is the original publisher URL. |
| Cluster | StTdZIrt_uZJ |
| Cluster logic | Grouped by semantic title/content similarity across sources within a rolling window. Same-publisher template collisions are excluded from coverage comparison. |
| Ranking reason | Story pages are not engagement-ranked. Hub feeds use recency, with optional source-diversified chronological ordering (cap consecutive stories per source). No personalized ranking. |
| Publisher visit | Yes — open original |
| Substitutes article? | No — link-out required for full text |
Rights status (four layers)
WeSearch handling by dimension
| Indexing | May the item be indexed (stored, ranked, made findable)? | Allowed |
| Snippet | May a short excerpt of the publisher's text be shown? | Allowed |
| AI summary | May WeSearch generate its own short summary of the article? | Limited |
| Retrieval / RAG | May the content be exposed for third-party retrieval-augmented generation? | Not asserted |
| Model training | May the content be used to train AI models? | Not asserted |
| Commercial reuse | May the content be reused commercially? | Not permitted |
Basis: Derived from the published RSS/Atom feed. Contact: [email protected]. Reviewed: 2026-07-24.
Opening excerpt (first ~120 words) tap to expand
TL;DR: CVE-2026-27771 allowed unauthenticated access to private container images on Gitea instances. 30,000+ deployments were affected. The flaw went undetected for 4 years. NoScope discovered and responsibly disclosed it. If you run Gitea Update to v1.26.2 immediately. If you can't update right now, set [service].REQUIRE_SIGNIN_VIEW=true in your Gitea configuration as a temporary stopgap. Note this stopgap isn't suitable if you intentionally expose some containers publicly. If your team runs Gitea and uses its built-in container registry, there's a question you should be asking right now: has anyone been reading your private images? Not because you misconfigured something. Not because someone phished your credentials.
…
Excerpt limited to ~120 words for fair-use compliance. The full article is at NoScope.
Discussion
0 commentsMore from NoScope
