Have you patched your multi-tenant Red Hat Quay registries for CVE-2026-110697?
CVE-2026-110697 is a Critical flaw in Red Hat Quay 3 and Quay 5, scored 9.9 and marked preliminary by Red Hat. A low-privilege tenant can retrieve other tenants' robot accounts and tokens due to unescaped pattern matching on namespace names, and matched robot accounts can be taken over or deleted. Red Hat has named fixed 3.x releases, with no errata listed yet, and has already fixed Quay.io. No fixed release is named for 3.11, 3.13 or Quay 5. Update now.
Update to a named 3.x release. No errata listed yet. Quay.io is already fixed. No fix named for 3.11, 3.13 or Quay 5. Not in CISA KEV when checked on 11 November 2026.
Red Hat names these fixed releases, with no errata listed yet: 3.9.28, 3.10.28, 3.12.24, 3.14.10, 3.15.9, 3.16.7, 3.17.7 and 3.18.3. It says Quay.io is already fixed. No fixed release is named for 3.11, 3.13 or Quay 5 when we checked. CVE-2026-110697 was not in CISA's Known Exploited Vulnerabilities catalogue when we checked at 18:09 GMT on 11 November 2026 (catalogue 2026.11.10, released at 19:03 UTC on 10 November, before this CVE was published). Recheck KEV. We make no claim either way about exploitation.
By Simon Phillips, CTO. Reviewed by Oliver Legg, Head of SOC and IR. Last updated 11 November 2026, 18:36 GMT.
At a Glance
Based on the official Red Hat CVE page, the official CVE record, Red Hat Bugzilla 2552237, the NVD record, and CISA KEV, as of 11 November 2026. Last updated 11 November 2026, 18:36 GMT.
Critical, CVSS 3.1 9.9
Red Hat rates CVE-2026-110697 Critical, CVSS 3.1 9.9, with vector CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:H/A:H, and describes that score as preliminary and subject to review. The NVD record was in Awaiting Analysis status when we checked, shows the Red Hat 9.9 as Primary, and has not scored it itself.
Named 3.x releases; no errata yet; not in CISA KEV
Red Hat has named fixed 3.x releases, with no errata listed yet, and says Quay.io is already fixed. No fixed release is named for 3.11, 3.13 or Quay 5 when we checked, and Bugzilla 2552237 was in NEW status with no fixed-in value. CVE-2026-110697 was not in CISA KEV when checked at 18:09 GMT on 11 November 2026 and again later the same day (catalogue 2026.11.10, which predates this CVE). Recheck KEV. We make no claim either way about exploitation.
Quay 3 and Quay 5
The official Red Hat CVE page and CVE record list Red Hat Quay 3 (packages quay/quay-rhel8 and quay/quay-rhel9) and Red Hat Quay 5 (package quay/quay-rhel9) as affected. They also list Red Hat OpenShift Update Service (package openshift-update-service-rhel8) as not affected, with the justification that the vulnerable code is not present. When we checked, the Quay packages still showed no advisory.
Named 3.x releases; no errata listed yet
Red Hat says to update to the fixed release named 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, and that Quay.io is already fixed. Those are fixed releases named by Red Hat; no errata is listed yet. No fixed release is named for 3.11, 3.13 or Quay 5 when we checked.
The official CVE record's timeline says the issue was reported to Red Hat on 14 October 2026 at 14:00 UTC.
CVE-2026-110697 is reserved.
The official CVE record's timeline lists the issue as made public on 11 November 2026 at 14:00 GMT. The Red Hat CVE page uses the same public date.
The official CVE record for CVE-2026-110697 is published. Red Hat rates it Critical, CVSS 3.1 9.9, and describes that score as preliminary and subject to review.
The NVD record is published, in Awaiting Analysis status, and shows the Red Hat 9.9 as Primary. NVD has not scored it itself.
CVE-2026-110697 is not in CISA KEV catalogue 2026.11.10 (released at 19:03 UTC on 10 November, before this CVE was published). Recheck KEV.
What the official records describe
Red Hat describes this as a Critical flaw that can break tenant isolation in multi-tenant Quay deployments. In high-level terms, a low-privilege tenant can retrieve other tenants' robot accounts and tokens due to unescaped pattern matching on namespace names, and matched robot accounts can be taken over or deleted. Official records list CWE-89. This issue was discovered by Red Hat. We do not reproduce the low-level request flow from the official description.
This is a separate issue from CVE-2026-123710, a different Red Hat Quay flaw that we published a guide for earlier today.
What to Do in the Next 24 Hours
Proactive on the left. Reactive on the right. Vendor steps and our advice are labelled separately.
Update, then reduce exposure
- Vendor path: update to the fixed release named by Red Hat for your version. Red Hat names 3.9.28, 3.10.28, 3.12.24, 3.14.10, 3.15.9, 3.16.7, 3.17.7 and 3.18.3. Those are fixed releases named by Red Hat; no errata is listed yet. It says Quay.io is already fixed. No fixed release is named for 3.11, 3.13 or Quay 5 when we checked. See the Red Hat CVE-2026-110697 page.
- Vendor path: if you cannot update immediately, Red Hat says to restrict who can create organisations 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 do not match expected robot usage. Red Hat says these steps reduce exposure but do not fix the underlying flaw.
- Our advice: patch multi-tenant and customer-shared registries first.
- Our advice: review self-registration (FEATURE_USER_CREATION is on by default), and check whether any Quay instance is reachable from the internet.
Hunt and contain
- Our advice: if misuse is found, rotate the affected robot tokens after patching, verify image digests, and check downstream deployments that may have pulled from the registry.
- Vendor path: Red Hat also says to rotate robot tokens for any namespace that collides with an underscore-containing one, and to monitor pulls or pushes that do not match expected robot usage.
- Our advice: keep audit logs and a record of robot accounts for investigation, and start incident response if images or tokens may have reached other systems or customers.
Proactive: Vendor Steps, Then Ours
Red Hat's fixed releases first, then Red Hat's interim steps, then our advice. Our advice is not a substitute for the official Red Hat CVE page, the official CVE record or NVD.
Update to a named fixed 3.x release
Red Hat's mitigation on the Red Hat CVE-2026-110697 page is to 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. Those are fixed releases named by Red Hat; no errata is listed yet. Red Hat says Quay.io is already fixed, and that there is no other complete workaround. No fixed release is named for 3.11, 3.13 or Quay 5 when we checked. When we checked, the packages table still listed Quay 3 and Quay 5 as Affected and showed no advisory.
If you cannot update immediately
Red Hat's interim steps, not ours: restrict who can create organisations 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 do not match expected robot usage. Red Hat says these steps reduce exposure but do not fix the underlying flaw.
Prioritise shared registries and review self-registration
Our advice, not Red Hat's wording: patch multi-tenant and customer-shared registries first. Review self-registration (FEATURE_USER_CREATION is on by default), and check internet exposure.
Free Detection Pack
Built by the CybaVerse threat hunt team for businesses, internal IT teams and MSPs. Check exposure offline and hunt for signs of misuse. Everything is read-only.
check-quay-cve-2026-110697.sh
Read-only, offline checker. It reads exported version, namespace and robot-account files that an admin hands over. It never contacts a registry or Red Hat, never runs Quay, writes nothing, and never prints or rotates tokens. Version verdicts are against the fixed release named by Red Hat for that stream, with no errata listed yet.
bash check-quay-cve-2026-110697.sh --version 3.17.6,registry.redhat.io/quay/quay-rhel9:v3.18.2
bash check-quay-cve-2026-110697.sh --namespaces orgs_and_users.json --robots robots.json --name site-aCheck-QuayCve2026110697.ps1
The same checks in PowerShell 7, with identical output and exit codes. It also runs under PowerShell on Linux. It never prints or rotates tokens.
pwsh -File Check-QuayCve2026110697.ps1 --version 3.17.6,registry.redhat.io/quay/quay-rhel9:v3.18.2KQL and Sigma
19 KQL hunts (Q1 to Q1g are inventory; Q2 to Q6 are our patterns). 5 Sigma rules, all our patterns. Only the two proxy Sigma rules convert on Sentinel ASIM. None of the KQL has been run against a live tenant yet.
Verdicts
- PATCHEDFull build at or above the fixed release named by Red Hat for that 3.x stream. No errata is listed yet.
- VULNERABLEFull build below the fixed release named by Red Hat for that stream.
- NO FIX NAMEDA Quay 3 stream Red Hat has not named a fix for (including 3.11 and 3.13), or Quay 5.
- OUT OF RANGENot Quay 3 or Quay 5.
- UNKNOWNThe version could not be read, for example a latest tag or a digest.
- COLLISION or ROTATEA namespace with an underscore matches another namespace, or a robot in a matched namespace was listed. Review it. The checker never prints or rotates tokens.
- NO FINDINGSNothing matched in the files that were supplied.
Exit codes
| Code | Meaning |
|---|---|
| 0 | NO FINDINGS |
| 1 | ACTION NEEDED (VULNERABLE, COLLISION or ROTATE) |
| 3 | UNKNOWN (UNKNOWN, NO FIX NAMED or OUT OF RANGE, and nothing worse) |
| 4 | Usage or read error |
The full pack zip contains 32 files.
Know the limits
- Both checkers are read-only and offline. They only read the files you point them at, send no network traffic, write nothing, run nothing, and never print or rotate tokens.
- Q2 to Q6, and all five Sigma rules, are our own patterns, not Red Hat's. Q1 to Q1g are inventory. None of these hunts prove exploitation.
- None of the KQL has been run against a live tenant.
- Only the two proxy Sigma rules convert on Sentinel ASIM. Other Microsoft pipelines have no table for the webserver rules, and no proxy table except that ASIM conversion. Use the KQL hunts where a rule does not convert.
What is in the pack
| File | What it does |
|---|---|
| check-quay-cve-2026-110697.sh | Read-only checker for Linux and macOS (bash) |
| Check-QuayCve2026110697.ps1 | The same checker in PowerShell 7 |
| KQL (19 hunts) | Q1 to Q1g inventory; Q2 to Q6 our patterns |
| Sigma (5 rules) | All our patterns; only the two proxy rules convert on Sentinel ASIM |
| tests/ | Fixtures and tests (in the full pack) |
| README.md | Verified facts, Red Hat vs our advice, limits and usage |
Reactive: How to Hunt (Our Advice)
The hunts below are CybaVerse advice, our own patterns. The detection pack on this page has not been run against a live tenant. CybaOps can still run a hunt across your estate.
Find unpatched and shared registries
Inventory Red Hat Quay 3 and Quay 5 registries, including quay-rhel8 and quay-rhel9 images, and identify multi-tenant or customer-shared deployments first. Confirm whether each instance is on a fixed release named by Red Hat, or on a stream with no named fix (including 3.11, 3.13 and Quay 5). These are our patterns for finding exposure, not official indicators.
Review robot use you cannot account for
Follow Red Hat's monitoring advice: look for robot pulls or pushes that do not match expected usage, and for namespaces that may collide with an underscore-containing name. If misuse is found, our advice is to rotate the affected tokens after patching, verify image digests, and check downstream deployments.
If you find signs of compromise (our advice)
- Rotate the affected robot tokens after patching, and any other credentials those robots protected.
- Verify image digests against what your build system pushed, and check downstream deployments that may have pulled from the registry.
- Keep audit logs, robot-account records and registry events for investigation.
- Start incident response if private images may have been read or if tags may have been replaced.
Red Hat Quay CVE-2026-110697 FAQ
Short answers based on the official Red Hat CVE page, the official CVE record, Red Hat Bugzilla 2552237, the NVD record, and CISA KEV, checked on 11 November 2026.
What is CVE-2026-110697?
The official Red Hat CVE record, published on 11 November 2026, covers Red Hat Quay 3 (quay-rhel8 and quay-rhel9) and Red Hat Quay 5 (quay-rhel9). In high-level terms, a low-privilege tenant can retrieve other tenants' robot accounts and tokens due to unescaped pattern matching on namespace names, and matched robot accounts can be taken over or deleted. Official records list CWE-89. This issue was discovered by Red Hat. This is a separate issue from CVE-2026-123710.
How severe is it?
Red Hat rates CVE-2026-110697 Critical, CVSS 3.1 9.9, with vector CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:H/A:H, and describes that score as preliminary and subject to review. The NVD record was in Awaiting Analysis status when we checked on 11 November 2026, shows the Red Hat 9.9 as Primary, and has not scored it itself.
Is this being exploited, or is it in CISA KEV?
CVE-2026-110697 was not in CISA's Known Exploited Vulnerabilities catalogue when we checked at 18:09 GMT on 11 November 2026 (catalogue 2026.11.10, released at 19:03 UTC on 10 November, before this CVE was published). Recheck KEV. We make no claim either way about exploitation.
Which software is affected, and is there a fix?
The official records list Red Hat Quay 3 and Red Hat Quay 5 as affected, and list Red Hat OpenShift Update Service as not affected. Red Hat names fixed 3.x releases 3.9.28, 3.10.28, 3.12.24, 3.14.10, 3.15.9, 3.16.7, 3.17.7 and 3.18.3. Those are fixed releases named by Red Hat; no errata is listed yet. Red Hat says Quay.io is already fixed. No fixed release is named for 3.11, 3.13 or Quay 5 when we checked. Bugzilla 2552237 was in NEW status with no fixed-in value.
What should we do first?
Follow Red Hat's path: update to a fixed release named by Red Hat. If you cannot update immediately, Red Hat says to restrict who can create organisations or namespaces containing an underscore, rotate robot tokens for colliding namespaces, and monitor unexpected robot pulls or pushes, and notes that these steps reduce exposure but do not fix the underlying flaw. Our advice: patch multi-tenant and customer-shared registries first, and review self-registration (FEATURE_USER_CREATION is on by default). If misuse is found, rotate affected tokens after patching, verify image digests, and check downstream deployments.
Who is this relevant to?
Organisations and MSPs that run multi-tenant or customer-shared Red Hat Quay 3 or Quay 5 registries. Official records also list Red Hat OpenShift Update Service as not affected. This issue is separate from CVE-2026-123710.
Protect Your Registries, and the Images They Hold
CybaOps monitors your servers, endpoints and cloud workloads, whether that's your own business or your clients'. UK-based analysts monitor alerts 24/7, run these threat hunts and act on pre-approved response actions, and CybaOps drives remediation through to a verified fix, so proactive checks and reactive response happen in one place.
Sources
- Red Hat: CVE-2026-110697 (Critical, CVSS 3.1 9.9, described as preliminary and subject to review; made public 11 November 2026, 14:00 GMT; page checked 11 November 2026)
- Official CVE record: CVE-2026-110697 (published 11 November 2026, 17:06 UTC)
- Red Hat Bugzilla 2552237 (status NEW when checked on 11 November 2026; no fixed-in value listed)
- NVD: CVE-2026-110697 (Awaiting Analysis; shows the Red Hat CVSS 3.1 9.9 as Primary; NVD has not scored it itself; published 11 November 2026, 17:17 UTC)
- CISA: Known Exploited Vulnerabilities catalogue (checked 11 November 2026, 18:09 GMT; catalogue 2026.11.10, released 10 November 2026 at 19:03 UTC)
This is a separate issue from Red Hat Quay CVE-2026-123710, which we published earlier today. All threat guides.