Critical Red Hat Quay Flaw Exposes Every Private Container Image in a Registry

Red Hat has disclosed and patched a critical vulnerability in its Quay container registry that allows an attacker with network access to the registry to read and overwrite private container images across every repository it hosts. The flaw is notable not just for its severity but for how little an attacker needs to exploit it.

According to the advisory summarized by The Hacker News, Quay ships with anonymous access enabled by default. While that setting remains on, an unauthenticated attacker can abuse the flaw without any account at all. If anonymous access has been disabled, the exposure narrows but does not disappear: any user holding a valid account can still exploit the issue. In practice, that means the registry's entire private image inventory—including images in repositories the attacker should never be able to touch—is at risk.

The impact goes beyond confidentiality. Because the flaw permits overwriting as well as reading, an attacker could replace trusted images with tampered ones. Container images are frequently pulled automatically by CI/CD pipelines, Kubernetes clusters, and production hosts, so a poisoned image can propagate quickly and quietly through an environment. That combination of read and write access to every repository makes this a supply chain concern as much as a registry permissions bug.

Fixed Builds Released

Red Hat has published fixed builds for eight Quay releases, and operators are urged to upgrade immediately. Given the breadth of the flaw—affecting all repositories rather than a single namespace—patching should be treated as urgent rather than routine. Organizations running Quay should also review their exposure while remediation is underway.

Mitigation Guidance

Where immediate patching is not possible, disabling anonymous access reduces the attack surface by removing the no-credential path. However, Red Hat's own description makes clear this is only a partial mitigation, since authenticated users can still trigger the flaw. Network-level restrictions—limiting who can reach the registry API—add another layer of defense, but neither substitute for the fix.

Administrators should also treat the window before patching as a potential compromise period. Recommended checks include:

  • Audit image digests and tags for unexpected changes, particularly in repositories that hold base images or deployment artifacts.
  • Review registry access logs for anomalous pulls, pushes, or API calls from unfamiliar sources.
  • Verify image signatures where signing is in use, and re-validate any images pulled during the exposure window.
  • Rotate credentials for accounts and service tokens with registry access if tampering is suspected.

Why This Matters for Container Supply Chains

Registries are high-value targets precisely because they sit upstream of everything else. A registry that cannot enforce repository-level isolation undermines the access controls teams believe they have configured. The default-on anonymous access setting in Quay compounds the problem: many deployments may never have consciously chosen to expose the registry, yet find themselves in the unauthenticated attack path by configuration default.

This incident fits a broader pattern of container infrastructure becoming a preferred entry point for attackers. Image registries, build systems, and artifact repositories are increasingly probed for weaknesses that allow silent substitution of trusted software. Defenders should assume that any registry reachable from untrusted networks is a candidate for this class of attack and should apply defense in depth: patching promptly, minimizing anonymous access, segmenting registry networks, and continuously verifying the integrity of what gets deployed.

For Quay operators, the immediate action is straightforward: identify your version, apply the fixed build, and confirm that anonymous access is disabled unless there is a documented business reason to keep it on. Then look backward at logs and image digests to establish whether anything changed before the patch landed.

The Bottom Line

A registry-wide read-and-write flaw in Red Hat Quay gives attackers a path to both steal and tamper with private container images, with unauthenticated exploitation possible under default settings. Fixed builds are available for eight releases. Patch now, restrict access in the interim, and audit your images for signs of tampering.

Original source: The Hacker News – Critical Red Hat Quay Flaw