A namespace can cross the tenant boundary
CVE-2026-110697 affects Red Hat Quay’s robot account listing function. Red Hat says user-controlled namespace names were used in a SQL LIKE pattern without escaping wildcard characters. An authenticated user could create a colliding namespace containing an underscore and retrieve robot account tokens from another tenant.
The stolen credentials may allow image pulls, pushes or overwrites. This matters when several teams or customers share a registry. Red Hat rates the issue Critical. Quay.io has been fixed, but self-managed deployments still need to check their product version.
Check namespaces and registry activity
Identify Quay versions and whether the deployment serves multiple tenants. Review namespaces with underscores and compare them with other tenant names that differ by one character. This helps locate possible token overlap while you prepare the update.
Review robot account activity for unexpected image pulls or pushes. Give special attention to CI systems and deployment pipelines that trust registry images. Preserve logs if you find activity that does not match an approved build or release.
Upgrade and rotate affected credentials
Red Hat lists fixed releases 3.9.28, 3.10.28, 3.12.24, 3.14.10, 3.15.9, 3.16.7, 3.17.7 and 3.18.3. Confirm which branch your Quay product uses and install the matching fixed release.
If the update cannot happen at once, Red Hat advises restricting creation of colliding underscore namespaces and rotating tokens for namespaces that may collide. These steps reduce exposure; they do not replace the update. Review image provenance after changing registry credentials.
