CVE-2026-110697: Red Hat Quay SQL injection in robot account listing

CVE-2026-110697 · Severity: critical · CVSS 9.9 · Published 2026-11-11

Red Hat Quay is a container registry used by enterprises to store and manage container images. A critical flaw allows an authenticated attacker to bypass tenant isolation by creating a namespace with an underscore character, which causes the system to leak robot account credentials from other organizations on the same registry. An attacker can then use these stolen credentials to read, modify, or inject malicious container images into other tenants' CI/CD pipelines, compromising the supply chain.

Technologies: Red Hat Quay. Vendors: Red Hat.

Quick answers

Is CVE-2026-110697 exploited in the wild?
No. Junglewise Threat Intelligence has no report of CVE-2026-110697 being exploited in the wild.
How severe is CVE-2026-110697?
Critical severity, with a CVSS score of 9.9, published 11 November 2026.
Which products and versions are affected?
Red Hat Quay versions before 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.
Is there a fix for CVE-2026-110697?
Yes: fixed in Red Hat Quay 3.9.28, 3.10.28, 3.12.24, 3.14.10, 3.15.9, 3.16.7, 3.17.7, 3.18.3. Until then: Restrict who can create organizations or namespaces containing an underscore character, rotate robot tokens for any namespace that collides with an underscore-containing one, and monitor registry activity for unexpected pulls or pushes. These steps reduce exposure but do not fix the underlying flaw. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
How is CVE-2026-110697 attacked?
It is attacked over the network.
Am I affected by CVE-2026-110697?
Check whether you run Red Hat Quay at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

How to fix

  • Fixed in: Red Hat Quay 3.9.28, 3.10.28, 3.12.24, 3.14.10, 3.15.9, 3.16.7, 3.17.7, 3.18.3

Restrict who can create organizations or namespaces containing an underscore character, rotate robot tokens for any namespace that collides with an underscore-containing one, and monitor registry activity for unexpected pulls or pushes. These steps reduce exposure but do not fix the underlying flaw.

Technical details

The robot account listing function constructs a SQL LIKE pattern from unescaped user-controlled namespace names, allowing an underscore to act as a single-character wildcard. An authenticated attacker creates a namespace containing an underscore that matches other tenants' namespaces, enabling enumeration and retrieval of encrypted robot tokens via SQL injection. The vulnerability requires authentication and affects multi-tenant deployments, with fixes available in versions 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.

Affected products

  • Red Hat Quay versions before 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

Timeline

  • 2026-11-11: disclosed
  • 2026-11-11: advisory

References

This page as Markdown. Free to reuse under CC BY 4.0 with a link back.