Copyright © 2012 Red Hat, Inc. All rights reserved. Critical 2026-11-11T14:00:00 quay: quay: SQL LIKE wildcard injection in robot listing leaks cross-tenant robot tokens 9.9 CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:H/A:H CWE-89

A flaw was found in Quay where the robot account listing function constructs a SQL LIKE pattern from user-controlled namespace names without escaping wildcard metacharacters. An attacker who creates a namespace containing an underscore character can match and retrieve robot accounts and their decrypted authentication tokens from other tenants' namespaces, leading to cross-tenant credential theft and unauthorized image operations.

A flaw was found in Quay where the robot account listing function constructs a SQL LIKE pattern from user-controlled namespace names without escaping wildcard metacharacters. An attacker who creates a namespace containing an underscore character can match and retrieve robot accounts and their decrypted authentication tokens from other tenants' namespaces, leading to cross-tenant credential theft and unauthorized image operations.

This flaw is rated Critical because it lets an authenticated attacker break tenant isolation in multi-tenant Quay deployments. By creating a namespace whose name contains an underscore that collides with an existing one, the attacker causes the underscore to act as a single-character SQL LIKE wildcard, matching the victim's namespace. This allows the attacker to list and steal the victim's robot account tokens, then use them to read, push, or overwrite that tenant's container images. No elevated privileges or victim interaction are required. In OpenShift environments where Quay serves as the integrated container registry, stolen robot credentials can be used to inject malicious images into CI/CD pipelines, putting the container supply chain across production clusters at risk. Multi-tenant Quay deployments are common in enterprises sharing a registry across teams and in service providers hosting multiple customer organizations. This issue was discovered by Dave O'Connor (Red Hat). Update to the fixed Red Hat Quay release for your version: 3.9.28, 3.10.28, 3.12.24, 3.14.10, 3.15.9, 3.16.7, 3.17.7, or 3.18.3. Red Hat has already fixed Quay.io. There is no other complete workaround. If you cannot update immediately, restrict who can create organizations or namespaces containing an underscore, rotate robot tokens for any namespace that collides with an underscore-containing one, and monitor registry activity for pulls or pushes that don't match expected robot usage. These steps reduce exposure but do not fix the underlying flaw. Red Hat Quay 3.10 2026-11-11T00:00:00Z RHSA-2026:99025 quay/quay-rhel8:1793993674 Red Hat Quay 3.12 2026-11-11T00:00:00Z RHSA-2026:99027 quay/quay-rhel8:1793993854 Red Hat Quay 3.14 2026-11-11T00:00:00Z RHSA-2026:99024 quay/quay-rhel8:1793993848 Red Hat Quay 3.15 2026-11-11T00:00:00Z RHSA-2026:99023 quay/quay-rhel8:1793993771 Red Hat Quay 3.16 2026-11-11T00:00:00Z RHSA-2026:99022 quay/quay-rhel9:1793993799 Red Hat Quay 3.17 2026-11-11T00:00:00Z RHSA-2026:99026 quay/quay-rhel9:1793993778 Red Hat Quay 3.18 2026-11-11T00:00:00Z RHSA-2026:99019 quay/quay-rhel9:1793993890 Red Hat Quay 3.9 2026-11-11T00:00:00Z RHSA-2026:99021 quay/quay-rhel8:1793993730 mirror registry for Red Hat OpenShift 2 Affected openshift/mirror-registry-rhel8 Red Hat Quay 5 Affected quay/quay-rhel9 https://www.cve.org/CVERecord?id=CVE-2026-110697 https://nvd.nist.gov/vuln/detail/CVE-2026-110697 https://access.redhat.com/solutions/7149592