{
  "id": 20447814,
  "title": "Critical Red Hat Quay Flaw Lets Attackers Read and Overwrite All Private Container Images in a Registry",
  "url": "https://urgent.news/2026/11/17/critical-red-hat-quay-flaw-lets-attackers-read-and-overwrite-all",
  "topic": "tech",
  "section": "Tech",
  "published": "2026-11-17T14:38:24.000Z",
  "source": {
    "name": "Lobsters",
    "slug": "lobsters",
    "url": "https://thehackernews.com/2026/11/critical-red-hat-quay-flaw-lets.html"
  },
  "original_language": "en",
  "account": "A critical vulnerability in Red Hat Quay allows attackers who can access a Quay registry to read and overwrite private container images in every repository within the system. Quay provides anonymous access by default, meaning an attacker can exploit the flaw without needing an account. However, if anonymous access is disabled, any user with a valid account can also take advantage of the vulnerability. Red Hat has released patches for eight Quay 3 branches to address the issue, which is tracked as CVE-2026-123710 and has a CVSS score of 9.8. The vulnerability stems from Quay's trust in certain keys to sign access tokens for image pushes and pulls. An attacker can add their own key to the list of trusted keys without any expiry date, enabling them to accept tokens signed with the key for any repository. This allows the attacker to retrieve private images and any secrets or credentials stored within them. They can also push or overwrite images, and the changes will propagate to all systems that later pull those images. The malicious key remains active even after restarts and can be used to delete the keys used by running Quay instances, causing authentication errors for normal pushes and pulls. The same flaw was disclosed simultaneously as another critical vulnerability, CVE-2026-110697, which allows a Quay user creating a namespace to steal robot account tokens belonging to other tenants. The attacker can then use these tokens to read, push, or overwrite the tenants' images. This flaw is due to a lack of escaping of wildcard characters in the SQL LIKE pattern used to build the namespace list. Red Hat discovered both vulnerabilities and recommends limiting who can create organizations or namespaces with an underscore, rotating robot tokens for affected namespaces, and monitoring for unusual pulls or pushes. The company also advises disabling anonymous access and updating to the patched versions of Quay to mitigate the risks associated with these vulnerabilities.",
  "summary": null,
  "key_points": [],
  "editors_take": null,
  "illustration": null,
  "coverage": {
    "outlets": 1,
    "also_reported_by": []
  },
  "ai_generated": true,
  "disclaimer": "Summaries, key points and the editor’s take are written by software from other outlets’ reporting and may contain errors — always check the linked original."
}