QUAY · CVE-2026-110697 · Other
FIX → 3.18.3 +7 ✓ verified
Quay builds a SQL LIKE match from namespace names without escaping underscores, which act as wildcards. An attacker who creates a namespace containing an underscore can retrieve robot accounts and their decrypted tokens from other tenants' namespaces.
first public Nov 11, 2026 · 2 sources
Could this affect your app?
Free first check from your website. Connect your repo for the full answer.
Self-hosted Red Hat Quay deployments (including Quay as the OpenShift integrated registry) where users can create namespaces or organizations. Any authenticated user can create a namespace with an underscore, which acts as a SQL wildcard, and read other tenants' robot tokens. Single-tenant installs where nobody untrusted can create namespaces can deprioritize it. Quay.io is already fixed by Red Hat.
Not affected if managed-hosting, single-tenant
Who cares auth-required, container-registry, multi-tenant, quay, self-hosted
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 page as .md · .json · CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:H/A:H
NVD data is provided by NIST and is public domain. Posts quoted belong to their authors.
Check it with your coding agent
It reads this page and tells you if your code is affected.
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.
Upgrade to 3.18.3 +7
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 (match your minor line)