Skip to content
NewA calmer, faster ZeroHour
StoryVulnerabilitycritical

Red Hat Quay flaws can expose and overwrite private container images

5 sources · 5 articlesFirst reported Updated ()
What's new

November 13: GBHackers says the November 11 advisory, updated November 12, names no fixed version and Bugzilla still lists the bug as NEW.

Merged summary · x-ai/grok-4.7 · rewritten as coverage arrivesSummaries by Vani AI

Two critical Red Hat Quay flaws can let attackers read or overwrite private images; whether a fixed release exists is disputed.

Red Hat disclosed two critical Quay flaws found by Dave O’Connor. CVE-2026-123710, rated 9.8, lets an attacker install a persistent trusted signing key and mint read and write tokens for any repository, exposing private images and secrets or replacing images and tags. SecurityWeek says any valid account can do this even with anonymous access off; Cyber Security News and The Hacker News say an anonymous token can work when anonymous access is on and untrusted clients can reach /keys. CVE-2026-110697, rated 9.9, lets a namespace creator steal other tenants’ robot tokens. The Hacker News says fixed Quay 3 builds exist and Quay.io is fixed for the second flaw; SecurityWeek, Cyber Security News, and GBHackers say no fixed version is named, and GBHackers says Bugzilla still marks remediation unfinished. No in-the-wild attacks are reported.

Key facts
  • CVE-2026-123710 is rated CVSS 9.8; CVE-2026-110697 is rated 9.9.
  • A planted signing key has no expiry and survives restarts and password resets.
  • Quay 3 and Quay 5 are affected where untrusted clients can reach the key service.
  • Stolen robot credentials can inject images into OpenShift CI/CD, Red Hat says.
  • Bugzilla 2568072 was opened November 6 at urgent priority and severity.
Analyze CVE-2026-123710 with Vani AIImpact, affected versions, exploitation, mitigations and detection

Timeline

dated events in the reporting · oldest first
  1. Nov 6, 2026Bugzilla 2568072 opened at urgent priority and severity. · GBHackers
  2. Nov 11, 2026Red Hat published CVE-2026-123710; related fixes were merged. · Cyber Security News
  3. Nov 12, 2026Red Hat updated the Quay advisory; no fixed version named. · GBHackers

What each outlet adds

beyond the shared facts
  • SecurityWeekSays a valid account works even if anonymous access is disabled.
  • Cyber Security NewsAnonymous token path, /keys exposure limit, and no known attacks.
  • The Hacker NewsDetails CVE-2026-110697 and claims fixed Quay 3 builds.
  • GBHackersBugzilla still NEW; advisory updated November 12 without a fix.

Coverage

oldest first · one row per article · UTC
  1. · 4d ago Canadian Centre for Cyber SecurityFirst report

    Red Hat products listed as vulnerable in advisory AV26-1136

    The November 9 notice covers many Red Hat products, mostly all versions, and tells admins to apply updates.

  2. · 2d ago SecurityWeek

    Critical Red Hat Quay flaw can expose and overwrite private images

    CVE-2026-123710 scores 9.8; any valid account can install a persistent signing key, and no fixed version is named.

  3. · 1d ago Cyber Security News

    Unauthenticated Red Hat Quay flaw lets attackers replace signing keys

    CVE-2026-123710 scores 9.8; anonymous tokens can install a non-expiring key when anonymous access is on, and no fix is named.

  4. · 1d ago The Hacker News

    Critical Red Hat Quay flaws expose private container images

    CVE-2026-123710 and CVE-2026-110697 let attackers read or overwrite images; anonymous access can be enough.

  5. · 1d ago GBHackers

    Red Hat Quay flaw lets unauthenticated attackers seize registry signing keys

    CVE-2026-123710 scores 9.8; Red Hat has published no fixed version, and Bugzilla still marks remediation unfinished.

Vulnerabilities in this story

All
CVEVulnerabilityCVSSEPSSSignalsPublished
CVE-2026-110697
SQL wildcard injection in Quay robot account listing
9.9—
CVE-2026-123710
Unauthenticated signing-key install in Red Hat Quay
9.8—