Skip to content
Fencer Intel
critical 9.9

CVE-2026-110697 json

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

published 16h ago modified 16h ago also EUVD-2026-123611

cvss
9.9
version 3.1, CNA
cisa kev
Not listed
not in CISA's catalog
epss
—
no EPSS score yet
public exploits
0
none known

Summary

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.

Is CVE-2026-110697 in your stack? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.

Check with Fencer

Vendor advisories

What the vendors themselves say about their products: affected, fixed or not affected, and what to do.

red hat product security vex CVE-2026-110697 updated cvss 9.9

quay: quay: SQL LIKE wildcard injection in robot listing leaks cross-tenant robot tokens

  • Red Hat Quay 3 quay/quay-rhel8, quay/quay-rhel9 Red Hat Quay 5 quay/quay-rhel9
    affected: workaround, no fix available
  • Red Hat OpenShift Update Service openshift-update-service/openshift-update-service-rhel8
    not affected: vulnerable code not present

Red Hat CSAF VEX © Red Hat, Inc., from https://security.access.redhat.com/data/csaf/v2/vex/; changed: reduced to product statuses and remediations. CC BY 4.0 · csaf

CVSS scores

assigned by version score vector
CNA 3.1 9.9 CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:H/A:H
NVD 3.1 9.9 CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:H/A:H

Affected products

  • Red Hat Red Hat OpenShift Update Service
  • Red Hat Red Hat Quay 3
  • Red Hat Red Hat Quay 5

Classification

Weakness
  • CWE-89 Improper Neutralization of Special Elements used in an SQL Command

References

Sources

Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.