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

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.

Timeline

Scores

EPSS (exploitation in 30 days)

0.74% · top 45% of all CVEs (13 Nov 2026)

CISA SSVC

Exploitation: none · Automatable: no · Technical impact: total

The list uses the assigner's score when there is one, then CISA's, then NVD's: Critical 9.9.

Affected products

• Project Quay · quay

  • affected < 3.9.28
  • affected 3.10.0 – < 3.10.28
  • affected 3.12.0 – < 3.12.24
  • affected 3.14.0 – < 3.14.10
  • affected 3.15.0 – < 3.15.9
  • affected 3.16.0 – < 3.16.7
  • affected 3.17.0 – < 3.17.7
  • affected 3.18.0 – < 3.18.3

• Red Hat · Red Hat Quay 3.10

  • unaffected 1793993674 – < *

• Red Hat · Red Hat Quay 3.12

  • unaffected 1793993854 – < *

• Red Hat · Red Hat Quay 3.14

  • unaffected 1793993848 – < *

• Red Hat · Red Hat Quay 3.15

  • unaffected 1793993771 – < *

• Red Hat · Red Hat Quay 3.16

  • unaffected 1793993799 – < *

• Red Hat · Red Hat Quay 3.17

  • unaffected 1793993778 – < *

• Red Hat · Red Hat Quay 3.18

  • unaffected 1793993890 – < *

• Red Hat · Red Hat Quay 3.9

  • unaffected 1793993730 – < *

• Red Hat · mirror registry for Red Hat OpenShift 2

  All versions: affected

• Red Hat · Red Hat Quay 5

  All versions: affected

What to do

Workaround: 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.

Sources

The same CVE in the primary databases and aggregators, to check against.

• CVE.org record (opens in a new tab)
• CVE List JSON (GitHub) (opens in a new tab)
• NVD (opens in a new tab)
• FIRST EPSS (opens in a new tab)
• EUVD EUVD-2026-123611 (opens in a new tab)
• OSV.dev (opens in a new tab)
• GitHub Advisories (opens in a new tab)
• CIRCL Vulnerability-Lookup (opens in a new tab)

Badge for a README or a ticket

[![CVE-2026-110697](https://cveledger.app/badge/CVE-2026-110697.svg)](https://cveledger.app/cve/CVE-2026-110697)

Record last updated 13 Nov 2026, 20:50 UTC.