Red Hat Quay SQL LIKE robot token Flaw CVE-2026-110697: Update Now
Published November 11, 2026 · Last updated November 11, 2026
Red Hat Quay CVE Critical Patch
The short version: CVE-2026-110697 is a critical-severity security flaw in Red Hat Quay SQL LIKE robot token. The National Vulnerability Database (NVD) published it on November 11, 2026, and the score it lists is 9.9 out of 10. When FraudMeNot checked on November 11, 2026, CISA had not added CVE-2026-110697 to its Known Exploited Vulnerabilities catalog, so there was no public U.S. government confirmation of attacks yet. A fix is available, which is why this page focuses on who should update and how.
CVE-2026-110697 is a critical SQL injection flaw in Red Hat Quay, the container image registry. According to Red Hat, the robot-account listing function builds a SQL LIKE pattern from a user-controlled namespace name and does not escape wildcard characters. An attacker who can create a namespace whose name contains an underscore can "match and retrieve robot accounts and their decrypted authentication tokens from other tenants' namespaces," then use those tokens to read, push, or overwrite another tenant's images. Red Hat published the issue on November 11, 2026, and listed fixed Quay 3 releases the same day.
How the attack works
Quay organizes images in namespaces (organizations). Robot accounts are machine credentials used to pull and push images. The listing path treats the namespace name as a SQL LIKE pattern. In LIKE, an underscore matches any single character. If an attacker creates a namespace that differs from a victim's namespace by an underscore in a colliding position, the pattern matches the victim's name.
Red Hat's advisory explains the rest: the attacker can then list and steal the victim's robot tokens, and with those tokens can read, push, or overwrite that tenant's container images. The attacker needs a normal authenticated account that can create a namespace; Red Hat says no elevated privileges and no action by the victim are required. The weakness is CWE-89, Improper Neutralization of Special Elements used in an SQL Command.
The damage is not limited to one registry login. Red Hat notes that in OpenShift environments where Quay is the integrated 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 is common, both in enterprises that share a registry across teams and in service providers that host more than one customer organization. Those are the deployments where tenant isolation is supposed to hold, and where this flaw breaks it.
Single-tenant registries, where only one organization exists and only trusted administrators can create namespaces, are in a narrower position: the attacker still needs an account that can create a colliding namespace. Red Hat's own interim advice is to restrict who can create organizations or namespaces that contain an underscore, which is aimed at that first step. Shared and hosted multi-tenant registries, and OpenShift clusters that use Quay as the platform registry, remain the cases Red Hat highlights.
The tracking bug is Red Hat Bugzilla 2552237, titled "SQL LIKE wildcard injection in robot listing leaks cross-tenant robot tokens." Red Hat also gives the issue a Critical rating on its own product-security scale, separate from the CVSS figure.
Affected products and the fix
Red Hat's CVE record and customer-portal advisory list Red Hat Quay 3 (the quay-rhel8 and quay-rhel9 packages) and Red Hat Quay 5 (quay-rhel9) as affected. Red Hat OpenShift Update Service is listed as not affected, because the vulnerable code is not present.
The same advisory tells operators to update to a fixed Red Hat Quay release for their version line: 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 says it has already fixed Quay.io, the hosted registry. Those fixed version numbers appear in the mitigation section. As of this writing, the affected-packages table still shows Quay 3 and Quay 5 as "Affected" and does not yet list a Red Hat Security Advisory (RHSA) identifier.
The mitigation list does not name a fixed release for Quay 5. Operators on Quay 5 should watch the Red Hat CVE page for a version or errata, and should not assume a 3.x package applies.
Red Hat says there is no other complete workaround. If an immediate update is not possible, it recommends restricting who can create organizations or namespaces that contain an underscore, rotating robot tokens for any namespace that collides with an underscore-containing one, and watching registry activity for pulls or pushes that do not match expected robot usage. Those steps reduce exposure; they do not fix the flaw.
Severity and who scored it
Red Hat, the CVE Numbering Authority for this issue, scored it CVSS 3.1 9.9 (Critical). The vector is CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:H/A:H: a network attack with low complexity, low privileges, no user interaction, and a changed scope, with high impact on confidentiality, integrity, and availability. The same 9.9 figure appears on cve.org. NVD had not published its own score when checked on November 11. The Red Hat advisory notes that its CVSS figures are "preliminary and subject to review." The flaw is not in CISA's Known Exploited Vulnerabilities catalog, and Red Hat does not say it has been exploited.
Red Hat credits Dave O'Connor of Red Hat with the discovery. The issue was reported to Red Hat on October 14, 2026, and the CVE was reserved the same day. Red Hat's public date is November 11, 2026 at 9:00 AM EST.
This is a different vulnerability from CVE-2026-123710, a critical unauthenticated signing-key issue in Quay that Red Hat also published on November 11. That issue still has no listed fixed version.
What to do
- Quay 3 operators: upgrade now. Move each registry to the fixed release for your line: 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. Then confirm the running version on every registry instance, including disconnected and air-gapped installs and any mirror that still pins an older image.
- Quay.io customers: confirm you are on the hosted service. Red Hat says Quay.io is already fixed. If you also run a self-managed Quay 3, that install still needs the upgrade above.
- Quay 5 operators: watch for a listed fix, and apply the interim steps. Red Hat lists Quay 5 as affected but has not named a fixed Quay 5 release. Follow the CVE page for an errata or version, restrict underscore-containing namespace creation, rotate robot tokens on colliding namespaces, and review unexpected pulls and pushes.
- Platform and security teams: treat stolen robot tokens as a credential incident until the upgrade is done. Rotate robot tokens for namespaces that could have collided, review recent image pushes for unexpected tags, and look at CI/CD systems that pull from the registry for images that should not have changed.
- Do not confuse this with CVE-2026-123710. That separate Quay flaw still lacks a fixed version. Its temporary advice is different: restrict access to the
/keysendpoint. Applying only one of these responses does not address the other.
- After the upgrade, keep an eye on the advisory. The Red Hat CVE page still shows the affected-packages table as "Affected" without an RHSA ID, and it flags the CVSS numbers as preliminary. Check that page for an errata number, a Quay 5 fix, or a score change after you have upgraded.
Sources: Red Hat Customer Portal advisory for CVE-2026-110697; CVE record CVE-2026-110697 published by Red Hat; NVD record for CVE-2026-110697.
What the official record says about CVE-2026-110697
The record was filed by redhat.com. In its own words: "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."
Why SQL LIKE robot token admins should care
Severity scores use the Common Vulnerability Scoring System (CVSS). the address listed on redhat.com rated CVE-2026-110697 9.9 (Critical) under CVSS 3.1. Reading that rating in everyday terms: it can be reached over a network, including the internet; an attacker needs a low-privilege account; no one has to click or open anything. If it is abused, the rated damage to keeping data private is high, to keeping data unaltered is high, and to keeping SQL LIKE robot token running is high. Scoring string: CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:H/A:H.
The type of bug behind CVE-2026-110697
NVD classifies it using MITRE's Common Weakness Enumeration:
- CWE-89, Improper Neutralization of Special Elements used in an SQL Command. MITRE describes this class of bug as follows: "The product constructs all or part of an SQL command using externally-influenced input from an upstream component, but it does not neutralize or incorrectly neutralizes special elements that could modify the intended SQL command when it is sent to a downstream component. Without sufficient removal or quoting of SQL syntax in user-controllable inputs, the generated SQL query can cause those inputs to be interpreted as SQL instead of ordinary user data. (Roles: Attack-Focused, Common-Name, Abbreviation, Attack-Focused)"
Vendor remediation for CVE-2026-110697
The vendor advisory remediation for operators of SQL LIKE robot token, quoted for this page, is: "Upgrade Red Hat Quay 3 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 for your release line. Quay.io is already fixed. Quay 5 is affected with no named fixed release yet; apply Red Hat's interim restrictions and watch the CVE page."
What to do about it
- Update now: Upgrade Red Hat Quay 3 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 for your release line. Quay.io is already fixed. Quay 5 is affected with no named fixed release yet; apply Red Hat's interim restrictions and watch the CVE page.
- Who should act: IT teams, managed service providers, and developers who run or ship SQL LIKE robot token. Check every place it runs, including servers, build systems, containers, and older machines nobody watches closely.
- Read the official advisory from Red Hat Quay (linked under Sources) for exact fixed builds and any temporary workaround if you cannot patch today.
- After patching, confirm the new version is actually running and review logs from November 11, 2026 onward for anything unusual.
- Home users: you do not need to buy or download anything because of CVE-2026-110697. A caller, text, or pop-up claiming your computer is "infected" with this CVE and asking for money or remote access is a scam.
CVE-2026-110697 record details from CISA and NVD
- Attack complexity for CVE-2026-110697: low
- CVE-2026-110697 CVSS scope: changed
- NVD sub-scores for CVE-2026-110697: exploitability 3.1, impact 6.0.
- Who mapped the weakness type: the address listed on redhat.com (Primary)
- References in the NVD record: 2.
Dates to know
- November 11, 2026: NVD publishes CVE-2026-110697.
- November 11, 2026: FraudMeNot checks the CISA KEV catalog; CVE-2026-110697 is not listed.
- November 11, 2026: most recent NVD update (record status: Awaiting Analysis).
Official references
Links listed in the NVD record (labels in brackets come from NVD):
Sources
General education only, not security advice. Facts checked against the sources above on the date shown.