CriticalVulnerabilityMonitoring

Red Hat Quay critical flaw CVE-2026-123710 exposes private images

Red Hat Quay CVE-2026-123710 (CVSS 9.8) lets attackers plant a signing key and read or overwrite images; block /keys and update.

Published
Updated
Fixed in
Fixed builds for eight Quay 3 branches reported by The Hacker News; version numbers not confirmed, and other outlets say no fixed version is named
Exploitation
No, Cyber Security News says nobody has reported attacks in the wild and one tracker has indexed no public exploit code

Live scores

CVE-2026-123710
EPSS
0.007
low predicted chance of attack
VEDAS
0.048
little exploit evidence
On CISA KEV
Not listed
Detection rule
No public rule yet
EPSS (chance of attack)
100.1CVE-2026-123710 EPSS over time2026-112026-11-17
VEDAS (exploit evidence)
100.5CVE-2026-123710 VEDAS over time2026-112026-11-17

Thin horizontal line: the “likely exploited” threshold (EPSS 0.10, VEDAS 0.5). Shaded “no data” areas are periods when cve-scores did not publish.

Live scores

CVE-2026-110697
EPSS
0.007
low predicted chance of attack
VEDAS
0.053
little exploit evidence
On CISA KEV
Not listed
Detection rule
No public rule yet
EPSS (chance of attack)
100.1CVE-2026-110697 EPSS over time2026-112026-11-17
VEDAS (exploit evidence)
100.5CVE-2026-110697 VEDAS over time2026-112026-11-17

Thin horizontal line: the “likely exploited” threshold (EPSS 0.10, VEDAS 0.5). Shaded “no data” areas are periods when cve-scores did not publish.

What happened

Red Hat published an advisory on November 11, 2026 for a critical flaw in Red Hat Quay, tracked as CVE-2026-123710 with a CVSS score of 9.8 (Cyber Security News, SecurityWeek). Red Hat describes it as an unauthenticated registry signing-key takeover through service key rotation (GBHackers).

According to Cyber Security News, Quay’s service key server checks that a rotation request carries a JWT signed by an approved key, with the right audience and issuer. It does not check that the token was issued for key rotation. An anonymous token from the /v2/auth endpoint passes, because the audience comes from a client-supplied service parameter. The Hacker News reports the same mechanism.

The attacker can then send their own key to the /keys endpoint. That key can be saved with no expiry date, and Quay trusts it immediately (Cyber Security News). Tokens signed with it give read and write access to any repository. SecurityWeek reports these consequences:

  • Private images, and any credentials or secrets stored in them, can be exposed.
  • Images that other systems later download can be overwritten.
  • The planted key survives registry restarts unless it is removed.
  • Key rotation deletes the legitimate instance key as a side effect, and the attacker key can delete replacement instance keys, which can stop legitimate pushes and pulls.

Red Hat’s Dave O’Connor found the flaw. The logic has been present since Quay’s first public commit, according to the Bugzilla report cited by The Hacker News.

The Hacker News also reports a second critical flaw disclosed at the same time, CVE-2026-110697 (CVSS 9.9). A Quay user who can create a namespace could steal other tenants’ robot account tokens. The cause is an unescaped underscore wildcard in an SQL LIKE pattern in the robot account listing code. SecurityWeek confirms the second CVE exists and says fixes for both were merged into the project’s GitHub repository on November 11.

Outlets differ on fixes:

  • The Hacker News says Red Hat has released fixed builds for eight Quay 3 branches. It also says the CVE entry still showed every Quay package as affected with no fix when checked, and that none of the eight advisories list CVE-2026-110697.
  • SecurityWeek, Cyber Security News and GBHackers say no fixed version is named.
  • The specific fixed version numbers are not confirmed in the sources.

Am I affected?

You are likely affected if you run Quay and untrusted clients can reach the key server.

  • Versions: Cyber Security News and The Hacker News say Red Hat lists Quay 3 and Quay 5 as affected. The Hacker News adds that this covers every version of both, and that Red Hat’s guidance names standalone installs, Quay deployed by the Quay Operator on OpenShift, and the mirror registry for Red Hat OpenShift.
  • Exposure: Cyber Security News says only deployments where /keys is reachable by untrusted clients are exposed. The Hacker News says any Quay instance that untrusted clients can reach is exposed, including internal registries.
  • Anonymous access: The Hacker News says Quay enables anonymous access by default. Cyber Security News ties the anonymous path to the FEATURE_ANONYMOUS_ACCESS setting. Turning anonymous access off does not protect you, because any valid Quay account can still exploit the flaw (SecurityWeek).
  • Exploitation: Cyber Security News says nobody has reported attacks in the wild, and one tracker notes no public exploit code has been indexed.

Quay.io is already fixed for CVE-2026-110697, according to The Hacker News. Whether Quay.io is affected by CVE-2026-123710 is not confirmed in the sources.

What to do now

  1. At the proxy or load balancer, block the /keys endpoint for everything except trusted internal components (The Hacker News, Cyber Security News).
  2. Search audit logs for service_key_rotate and service_key_delete events where expiration_date is null (Cyber Security News).
  3. Remove any approved service keys you do not recognize. Password resets and robot token regeneration do not invalidate an unauthorized signing key (SecurityWeek).
  4. Keep the /keys block in place until a fixed build is running. Until then an attacker can install a new key the same way, so deleting one does not last (The Hacker News).
  5. Install the fixed release for your branch and watch Red Hat’s advisory for patch availability, since the sources disagree on whether fixed versions have shipped (GBHackers).
  6. GBHackers also suggests auditing recent image pushes and tag changes, and verifying image integrity before deployment by pinning images by digest rather than by mutable tags (GBHackers).
  7. For CVE-2026-110697, until you can update, Red Hat suggests limiting who can create organizations or namespaces containing an underscore, rotating robot tokens for any namespace that matches an underscore namespace, and watching for pulls or pushes that do not fit normal robot use. These steps reduce exposure but the flaw remains (The Hacker News).

Update, 17 November 2026

  • The Hacker News says the upstream fix adds the missing rotation check, requires keys added through the key server to have an expiry date, and stops callers from choosing a token’s audience. The same change also fixes the robot account search flaw. (thehackernews.com)
  • The Hacker News says Red Hat’s CVE page for CVE-2026-110697 names the same eight releases as fixed, calls updating the only complete fix, and says Quay.io is already fixed. (thehackernews.com)
  • The Hacker News says that for CVE-2026-110697 the attacker needs no elevated privileges and the victim does not have to do anything. Stolen robot credentials can be used to inject malicious images into CI/CD pipelines where Quay is the integrated registry for OpenShift, according to Red Hat. (thehackernews.com)
  • SecurityWeek says Red Hat’s advisory and Bugzilla report do not identify a fixed version for CVE-2026-123710, and that Red Hat warns attackers could reinstall malicious keys until a fix is deployed. (securityweek.com)

Sources