<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>cybercrime.club</title><link>https://cybercrime.club/tags/container-registry/</link><description>Infrastructure security news for people who build infrastructure.</description><generator>Hugo -- gohugo.io</generator><language>en-us</language><lastBuildDate>Wed, 27 May 2026 23:08:45 -0400</lastBuildDate><atom:link href="https://cybercrime.club/tags/container-registry/" rel="self" type="application/rss+xml"/><item><title>Gitea CVE-2026-27771: Container Registry Hands Out Private Images Without Authentication, 30,000 Instances Exposed</title><link>https://cybercrime.club/posts/gitea-cve-2026-27771-container-registry-private-images-unauth-pull/</link><pubDate>Wed, 27 May 2026 23:08:45 -0400</pubDate><guid>https://cybercrime.club/posts/gitea-cve-2026-27771-container-registry-private-images-unauth-pull/</guid><description>A four-year-old flaw in Gitea's OCI container registry lets anyone on the internet pull images marked private. 30,000+ deployments are exposed, Forgejo inherits the bug, and the only real fix is upgrading to 1.26.2 or forcing sign-in for all content.</description><category>vulnerability</category></item></channel></rss>