cve.bz

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

9.9 criticalEPSS 0.7%Fix available

Critical (9.9). EPSS 0.7% estimated probability of exploitation activity in the next 30 days.

On this page
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.

Severity

CVSS 3.1

9.9 critical
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:H/A:H
EPSS
0.7% estimated probability of exploitation activity in the next 30 days; 55th percentile. Scored 2026-11-13. A forecast for this CVE across the internet, not for your own systems.
CISA's assessment (SSVC)
Exploitation: none · Automatable: no · Technical impact: total, assessed 2026-11-12. From CISA's Vulnrichment in the CVE List: whether it is exploited, whether exploiting it can be automated, and how much control it gives.
CWE
CWE-89 Improper Neutralization of Special Elements used in an SQL Command (SQL Injection)
OWASP Top 10
A05:2025 Injection
Published
Modified
Assigned by
redhat (CNA)
NVD analysis
Awaiting analysis
Record from
the NVD, synced

Ask an AI about this CVE

ChatGPTClaudeGoogle AI Mode

Show the promptExplain CVE-2026-110697 for an engineer deciding whether to act. Use https://cve.bz/api/public/cves/CVE-2026-110697?via=ask-ai-copy and https://cve.bz/cve/CVE-2026-110697?via=ask-ai-copy as the source of truth: what is affected and which versions fix it, whether it is in CISA KEV, public exploits, and its EPSS (an internet-wide 30-day estimate of exploitation activity, not a forecast for my systems). If they give no fixed versions, use the CVE record https://cveawg.mitre.org/api/cve/CVE-2026-110697 or the vendor advisory, not third-party mirrors. Tell me how to check whether I am affected and how to verify a fix. Cite the sources and say where they are uncertain.

Opens a third-party assistant; its answer is its own, not cve.bz's. The prompt holds only this CVE's id and public links.

Badge for a README or a site

CVE-2026-110697

An image that stays current: it is drawn from the data each time it is fetched (a host that proxies images, as GitHub does, may show its copy for a while). Markdown:

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

HTML:

<a href="https://cve.bz/cve/CVE-2026-110697"><img src="https://cve.bz/cve/badge/CVE-2026-110697.svg" alt="CVE-2026-110697"></a>

Affected

  • project quay:quay
  • red hat:mirror registry for red hat openshift 2
  • red hat:red hat quay 3.10
  • red hat:red hat quay 3.12
  • red hat:red hat quay 3.14
  • red hat:red hat quay 3.15
  • red hat:red hat quay 3.16
  • red hat:red hat quay 3.17
  • red hat:red hat quay 3.18
  • red hat:red hat quay 3.9
  • red hat:red hat quay 5

Versions

From the CNA's record in the CVE List.

ProductAffected
Project Quay quaybefore 3.9.28
Project Quay quayfrom 3.10.0 before 3.10.28
Project Quay quayfrom 3.12.0 before 3.12.24
Project Quay quayfrom 3.14.0 before 3.14.10
Project Quay quayfrom 3.15.0 before 3.15.9
Project Quay quayfrom 3.16.0 before 3.16.7
Project Quay quayfrom 3.17.0 before 3.17.7
Project Quay quayfrom 3.18.0 before 3.18.3

Fixed in

ProductFixed in
Red Hat Quay 3.101793993674
Red Hat Quay 3.121793993854
Red Hat Quay 3.141793993848
Red Hat Quay 3.151793993771
Red Hat Quay 3.161793993799
Red Hat Quay 3.171793993778
Red Hat Quay 3.181793993890
Red Hat Quay 3.91793993730

Fix and patched versions

  • Red Hat Red Hat Quay 3.10: fixed in 1793993674
  • Red Hat Red Hat Quay 3.12: fixed in 1793993854
  • Red Hat Red Hat Quay 3.14: fixed in 1793993848
  • Red Hat Red Hat Quay 3.15: fixed in 1793993771
  • Red Hat Red Hat Quay 3.16: fixed in 1793993799
  • Red Hat Red Hat Quay 3.17: fixed in 1793993778
  • Red Hat Red Hat Quay 3.18: fixed in 1793993890
  • Red Hat Red Hat Quay 3.9: fixed in 1793993730

Linux distributions

DistributionReleasePackageFixed inAdvisory
Ubuntu16.04:LTS, 18.04:LTS, 20.04:LTS and 4 moredataquayno fix listedUBUNTU-CVE-2026-110697

From the distributions' data via OSV.dev: Ubuntu Security Notices © Canonical Ltd., CC BY-SA 4.0. Modified: reformatted and linked to CVE records. Credits. On the distributions' own pages: Ubuntu.

Red Hat

Red Hat rates this Critical.

Red Hat's statement

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.

Red Hat's mitigation

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.

ProductPackageStateAdvisory
Red Hat Quay 3.10quay/quay-rhel8:1793993674Fixed 2026-11-11RHSA-2026:99025
Red Hat Quay 3.12quay/quay-rhel8:1793993854Fixed 2026-11-11RHSA-2026:99027
Red Hat Quay 3.14quay/quay-rhel8:1793993848Fixed 2026-11-11RHSA-2026:99024
Red Hat Quay 3.15quay/quay-rhel8:1793993771Fixed 2026-11-11RHSA-2026:99023
Red Hat Quay 3.16quay/quay-rhel9:1793993799Fixed 2026-11-11RHSA-2026:99022
Red Hat Quay 3.17quay/quay-rhel9:1793993778Fixed 2026-11-11RHSA-2026:99026
Red Hat Quay 3.18quay/quay-rhel9:1793993890Fixed 2026-11-11RHSA-2026:99019
Red Hat Quay 3.9quay/quay-rhel8:1793993730Fixed 2026-11-11RHSA-2026:99021
Red Hat Quay 5quay/quay-rhel9Affected

Contains Red Hat Security Data © Red Hat, Inc., licensed under CC BY 4.0. Source: https://access.redhat.com/security/data. Modified: reformatted. Red Hat's page for CVE-2026-110697.

GitHub PoC (unverified)

Repositories on GitHub named after this CVE. Nobody has checked them and they are not scanned: some hold a working proof of concept, some nothing useful, and some malware made to look like one. Read the code before you run any of it.

  • googlesky/CVE-2026-110697 0 stars, Python, created
    Proof-of-concept and containerized differential lab for CVE-2026-110697: Red Hat Quay builds robot-listing SQL LIKE patterns from the calle…

Attack patterns (CAPEC)

  • CAPEC-7 Blind SQL Injection Likelihood: High · Severity: High
  • CAPEC-66 SQL Injection Likelihood: High · Severity: High
  • CAPEC-108 Command Line Execution through SQL Injection Likelihood: Low · Severity: Very High
  • CAPEC-109 Object Relational Mapping Injection Likelihood: Low · Severity: High
  • CAPEC-110 SQL Injection through SOAP Parameter Tampering Likelihood: High · Severity: Very High
  • CAPEC-470 Expanding Control over the Operating System from the Database Severity: Very High

The attack patterns MITRE's CAPEC relates to this record's weaknesses, as MITRE names them. Credits.

References

Check your stackJSON