RED HAT · Vendor
NO FIX YET
Quay.io, Red Hat's hosted container registry, had a degraded period in which some write operations failed and the registry went read-only to protect data. The sources say the cause was database scaling, and that it was resolved with no data loss; security scanning remained under maintenance afterward.
first public Sep 14, 2026 · 1 source
Check it with your coding agent
It reads this page and tells you if your code or app is affected.
Teams that push or pull images on Quay.io, the hosted Red Hat registry, were affected during the incident window; the sources describe an operational outage, not a vulnerability. The sources do not say whether any customer action is needed, and they give no version or configuration to check.
Not affected if no-quay-usage, self-hosted-quay
Who cares containers, quay.io, red-hat, redhat, security
Unknown from the sources.
No fix yet, per the sources.
Quay.io registry is operational since 15 Sep 2026, 5:00 AM UTC. Security scanning remains on maintenance until further notice.
During the incident, some write operations were failing. The registry was put into read-only mode to preserve data integrity. The underlying issue was related to database scaling and was resolved successfully without any data loss.
Are you affected?
Ask from here. InfraStack checks the affected versions against your stack and answers in your inbox.
InfraStack checks the affected versions against your stack and answers in Slack, with the evidence and the fix.
InfraStack checks it against your stack and answers on your report, with the evidence and the fix.