CVE-2026-110697

Quay: quay: sql like wildcard injection in robot listing leaks cross-tenant robot tokens

  • Critical 9.9

Description

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.

Key facts

Published
11 Nov 2026
Last changed
13 Nov 2026
Assigned by
redhat
EPSS
0.741% likely to be exploited in the next 30 days, higher than 55.198% of CVEs (scores for 15 Nov 2026)
SSVC (CISA)
Exploitation: none; Automatable: no; Technical impact: total

Severity scores

Each score is shown as its source gave it. They are not averaged or merged.

  • 9.9CVSS 3.1, Criticalfrom the CNA (redhat)CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:H/A:H

What to do

  • 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.CNA workaround statement

Historical context and remediation

This reference retains the original CVE publication date. A recent record update does not mean a new attack occurred.

No separately sourced impact summary is available on this page yet. Consult the description, version data and dated exploitation evidence.

Version statuses below come from the CNA. An “unaffected” version is not necessarily a currently supported release or proof of a patch date. EPSS is a dated risk estimate, not a count of historical attacks.

Read the original CVE record.

Affected products

VendorProductVersions
Project Quayquay
  • Default status: unaffected
  • 0 up to but excluding 3.9.28 (affected)
  • 3.10.0 up to but excluding 3.10.28 (affected)
  • 3.12.0 up to but excluding 3.12.24 (affected)
  • 3.14.0 up to but excluding 3.14.10 (affected)
  • 3.15.0 up to but excluding 3.15.9 (affected)
  • 3.16.0 up to but excluding 3.16.7 (affected)
  • 3.17.0 up to but excluding 3.17.7 (affected)
  • 3.18.0 up to but excluding 3.18.3 (affected)
Red HatRed Hat Quay 3.10
  • Default status: affected
  • 1793993674 up to but excluding * (unaffected)
Red HatRed Hat Quay 3.12
  • Default status: affected
  • 1793993854 up to but excluding * (unaffected)
Red HatRed Hat Quay 3.14
  • Default status: affected
  • 1793993848 up to but excluding * (unaffected)
Red HatRed Hat Quay 3.15
  • Default status: affected
  • 1793993771 up to but excluding * (unaffected)
Red HatRed Hat Quay 3.16
  • Default status: affected
  • 1793993799 up to but excluding * (unaffected)
Red HatRed Hat Quay 3.17
  • Default status: affected
  • 1793993778 up to but excluding * (unaffected)
Red HatRed Hat Quay 3.18
  • Default status: affected
  • 1793993890 up to but excluding * (unaffected)
Red HatRed Hat Quay 3.9
  • Default status: affected
  • 1793993730 up to but excluding * (unaffected)
Red Hatmirror registry for Red Hat OpenShift 2
  • Default status: affected
Red HatRed Hat Quay 5
  • Default status: affected

Timeline

  1. 14 Oct 2026 Reported to Red Hat.
  2. 11 Nov 2026 Made public.
  3. 11 Nov 2026 Published

Weakness

Practice this bug class

HackZoneLabs has a hands-on lab on SQL injection (CWE-89).

References