---
id: "CVE-2026-110697"
page: "https://infrastack.ai/live/CVE-2026-110697"
kind: "vulnerability"
aliases: ["CVE-2026-110697"]
title: "Quay: robot account listing leaks other tenants' credentials via SQL wildcard"
severity: "critical"
cvss: 9.9
epss: null
exploited: false
status: "open"
category: "other"
products: [{"name": "quay", "fixed": ["3.9.28", "3.10.28", "3.12.24", "3.14.10", "3.15.9", "3.16.7", "3.17.7", "3.18.3"], "affected": "unknown lower bound; fixed in 3.9.28, 3.10.28, 3.12.24, 3.14.10, 3.15.9, 3.16.7, 3.17.7, 3.18.3", "ecosystem": "vendor"}]
ecosystems: []
tags: ["auth-required", "container-registry", "multi-tenant", "other", "quay", "self-hosted"]
not_affected_if: ["managed-hosting", "single-tenant"]
published_at: "2026-11-11T17:17:14+00:00"
first_seen_at: "2026-11-11T17:28:20+00:00"
updated_at: "2026-11-11T17:30:09+00:00"
sources: [{"source": "nvd", "url": "https://nvd.nist.gov/vuln/detail/CVE-2026-110697", "first_seen_at": "2026-11-11T17:28:20+00:00"}, {"source": "analyst", "url": "https://access.redhat.com/security/cve/CVE-2026-110697", "first_seen_at": "2026-11-11T17:30:09+00:00", "cites": ["https://access.redhat.com/security/cve/CVE-2026-110697"]}]
exploit_sources: []
---

# Quay: robot account listing leaks other tenants' credentials via SQL wildcard

Link for people: https://infrastack.ai/live/CVE-2026-110697 (this .md is for agents)

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.

_Summary, check and fix written by a model from the sources; labelled as such._

## Affected

- vendor:quay affected unknown lower bound; fixed in 3.9.28, 3.10.28, 3.12.24, 3.14.10, 3.15.9, 3.16.7, 3.17.7, 3.18.3 fixed 3.9.28, 3.10.28, 3.12.24, 3.14.10, 3.15.9, 3.16.7, 3.17.7, 3.18.3

## How to check

Check your Red Hat Quay version (self-hosted, multi-tenant) against the fixed releases for your minor line. If users can create organizations/namespaces, you are exposed. Review whether any namespace containing an underscore exists that could collide with another namespace.

## Fix

Update Red Hat Quay to 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). Red Hat says Quay.io is already fixed. If you cannot update: restrict who can create organizations/namespaces with underscores, rotate robot tokens for namespaces that collide with an underscore-containing one, and watch for unexpected pulls/pushes (Red Hat: reduces exposure, not a fix).

## Timeline

- 2026-11-11T17:28:20+00:00 nvd https://nvd.nist.gov/vuln/detail/CVE-2026-110697
- 2026-11-11T17:30:09+00:00 analyst https://access.redhat.com/security/cve/CVE-2026-110697 — Red Hat CVE page read: authenticated user (PR:L) creating underscore namespace; fixed Quay releases listed; lower affected bound not stated; exploitation/PoC not checked beyond advisory.

## Documents

- [advisory] Red Hat CVE-2026-110697 https://access.redhat.com/security/cve/CVE-2026-110697

## From the sources

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.

---

_Free to read, with fair use of about 60 pages a minute. For higher limits or API access: sales@infrastack.ai_