CVE
Quay: quay: sql like wildcard injection in robot listing leaks cross-tenant robot tokens
Affects Red Hat Quay 3 and Red Hat Quay 5 installs older than the fixed releases. Update 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.
Written by anthropic/claude-haiku-5.5 from the sources below. Verify against them.
- Exploited
- No known exploitation
- Fix
- Fixed in 3.9.28, 3.10.28, 3.12.24, 3.14.10, 3.15.9, and 3 more
- Who is exposed
- Specific setups only
Do first: Check whether your setup matches what the bug needs. An attacker can create a namespace whose name contains an underscore that collides with an existing namespace. Quay installs older than the fixed Red Hat Quay releases are affected.
- Last modified
- Whether it needs action now or is a reference record, by fixed rules, with why. Last checked is when cve.now last re-read it.What do these mean? →
- Reference
- Last checked
- A 0-100 score for how much a CVE matters across the industry: exploitation, exposure, how widely the software is used, severity and whether a fix exists.What do these mean? →
- 28/100 · provisional
- How many real-world setups can hit the bug, from the vendor's advisory and CISA data. It does not know your setup.What do these mean? →
- Specific setups only
- Whether working attack code is public (Exploit-DB, Metasploit, Nuclei or GitHub). Public code makes attacks easier.What do these mean? →
- None on Exploit-DB, Metasploit or GitHub
Summary
Red Hat Quay and Red Hat OpenShift Update Service have a flaw in the robot account listing function, which builds a database search pattern from namespace names without escaping wildcard characters. A remote attacker with a low-privilege account can create a namespace containing an underscore to retrieve other tenants' robot accounts and their decrypted tokens, which allows credential theft and unauthorized image operations.
Read the original 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.
Who should check
Teams running Red Hat Quay 3.x or 5.x, or OpenShift Update Service, with registries shared across multiple tenants, teams or customer organizations.
Not fixed by: Restricting namespace creation or rotating tokens does not fix the flaw.
cve.now Index
- Exploitation?/40Unknown. No CISA SSVC exploitation rating yet
- Exposure8/25Specific setups only, reachable over the network
- Reach10/20Shipped in major Linux distributions
- Severity9.9/10CVSS 9.9
- No patch0/5No signal
What would change the score
- Would score about 78 if added to CISA KEV
- Would score about 73 if CISA's SSVC rates exploitation active
- Would score about 35 if CISA's SSVC rates it automatable
What to do
Check whether your setup matches what the bug needs.
An attacker can create a namespace whose name contains an underscore that collides with an existing namespace. Quay installs older than the fixed Red Hat Quay releases are affected.Upgrade to a fixed version: 3.9.28, 3.10.28, 3.12.24, 3.14.10, 3.15.9, or one of 3 more.
Workaround: 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. These steps reduce exposure but do not fix the flaw.
Check your systems with an agent
Paste this into a coding or ops agent. It checks your systems read-only and reports a table per asset.
Check whether my systems are affected by CVE-2026-110697 (Quay: quay: sql like wildcard injection in robot listing leaks cross-tenant robot tokens), using the cve.now data below.
Rules: work read-only. Do not run exploit code, proof-of-concept scripts or scanners that send attack payloads, and do not change any configuration, package, image or deployment. Report findings only.
What cve.now has for CVE-2026-110697 (entry last updated 2026-11-11):
Affected:
- Red Hat Red Hat OpenShift Update Service: version range not reported
- Red Hat Red Hat Quay 3: version range not reported
- Red Hat Red Hat Quay 3: version range not reported
- Red Hat Red Hat Quay 5: version range not reported
Fixed versions: 3.9.28, 3.10.28, 3.12.24, 3.14.10, 3.15.9, 3.16.7, 3.17.7, 3.18.3.
Conditions (all must be true for the bug to be hit):
- An attacker can create a namespace whose name contains an underscore that collides with an existing namespace. (source: https://access.redhat.com/security/cve/cve-2026-110697)
- Quay installs older than the fixed Red Hat Quay releases are affected. (source: https://access.redhat.com/security/cve/cve-2026-110697)
Setup: unknown whether the bug needs a non-default feature or setting. Check the advisory.
Attacker needs: network access, low-privilege login, no user action.
Workaround: 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. These steps reduce exposure but do not fix the flaw. (source: https://access.redhat.com/security/cve/cve-2026-110697)
CISA KEV: CVE-2026-110697 is not listed as of cve.now's last read.
This KEV status is for CVE-2026-110697 only. If you also check another CVE, look up its own KEV status; never assume it from this one.
How to check:
- Installed software: check what is actually running, not what a repo declares. Read the version from each host, container image and Kubernetes node (the binary's version output, the OS package database, image layers), and check whether the conditions above hold there. Distribution packages may carry a backported fix under an older version number; confirm against the distribution's own advisory.
Verify against the linked advisories before concluding, and cite the date you read each one:
- https://bugzilla.redhat.com/show_bug.cgi?id=2552237
- https://access.redhat.com/security/cve/CVE-2026-110697
- https://access.redhat.com/security/cve/cve-2026-110697
Do not conclude an asset is unaffected unless you checked it and the evidence covers both its version and the conditions above. If you could not check something, mark it unknown and say what is missing.
Report a table with one row per asset and these columns: Asset | Version or build | Status (affected, fixed, not applicable, unknown) | Compensating controls | Exposure (internet-facing, internal, none) | Evidence | Next action.
Entry: https://cve.now/CVE-2026-110697
For follow-up questions, use the cve.now MCP server at https://mcp.cve.now/mcp (no authentication), for example execute with name cve.get and arguments {"id": "CVE-2026-110697"}.Timeline
- CVE published
- First seen by cve.now
- Posted on X by cve.now
Affected versions
- openshift-update-service/openshift-update-service-rhel8
Version range not reported
- quay/quay-rhel8
Version range not reported
- quay/quay-rhel9
Version range not reported
- quay/quay-rhel9
Version range not reported
Evidence 4
CVE record · 2
Establishes: The identifier and description.
- Record
- Record
Write-ups · 1
Establishes: Technical detail and context.
- Report
Other links · 1
- Link
Corrections
None so far.
Something wrong on this page? Report an error. Every fix is listed here.
Questions about CVE-2026-110697
Is CVE-2026-110697 being exploited?
It is not in CISA's Known Exploited Vulnerabilities catalog, and CISA's SSVC assessment does not mark exploitation as active. That does not mean it has not been attacked: vendors and researchers can report attacks before CISA lists them. No public exploit code is tracked.Source: cve.now feed data
What does this mean?
An attacker can create a namespace whose name contains an underscore, which collides with an existing namespace because of how SQL LIKE wildcards are matched. Robot listing then exposes another tenant's robot account tokens, which can be used to read, push, or overwrite that tenant's container images.Source: access.redhat.com
Am I affected, and how do I check?
Red Hat Quay 3 and Red Hat Quay 5 installs older than the fixed releases are affected, and the flaw needs a namespace containing an underscore that collides with an existing one. Check the installed Quay version against the fixed releases listed in the advisory.Source: access.redhat.com
How do I fix CVE-2026-110697?
Update to the fixed Red Hat Quay release for the installed 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.Source: access.redhat.com