[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"$fDqp8AsBA9HyUooO_dBTG8-MTaRwCfDP7whH5FptW4Rk":3},{"article":4,"iocs":41,"watch_terms":49,"solutions":50,"lesson":140},{"id":5,"title":6,"slug":7,"summary":8,"ai_summary":9,"brief":10,"url":11,"image_url":12,"published_at":13,"ingested_at":14,"relevance_score":15,"entities":16,"category_id":23,"category":24,"article_tags":28},"53b468a6-6df9-4b73-b04c-c8523c188976","Critical Red Hat Quay Vulnerability Could Expose Private Container Images","critical-red-hat-quay-vulnerability-could-expose-private-container-images-a84ff7","Attackers could exploit a critical Red Hat Quay flaw to steal private container images, overwrite repositories and maintain persistent access. The post Critical Red Hat Quay Vulnerability Could Expose Private Container Images appeared first on SecurityWeek.","A critical vulnerability (CVE-2026-123710) in Red Hat Quay, a container registry, allows unauthenticated attackers to take over registry token signing. This enables them to generate tokens with read\u002Fwrite access to any repository, exposing private images and secrets, and allowing them to overwrite images. While fixes are merged, Red Hat advises restricting access to the key-management service and reviewing logs.","Red Hat Quay vulnerability CVE-2026-123710 allows attackers to steal private container images.","https:\u002F\u002Fwww.securityweek.com\u002Fcritical-red-hat-quay-vulnerability-could-expose-private-container-images\u002F","https:\u002F\u002Fwww.securityweek.com\u002Fwp-content\u002Fuploads\u002F2025\u002F10\u002FRed-Hat.jpeg","2026-11-12T09:23:21+00:00","2026-11-12T10:00:14.929326+00:00",8,[17,20],{"name":18,"type":19},"Red Hat Quay","product",{"name":21,"type":22},"Red Hat","vendor","80544778-fabb-4dcd-aa35-17492e5dcf4f",{"id":23,"icon":25,"name":26,"slug":27},null,"Vulnerabilities","vulnerabilities",[29,34,36],{"category":30},{"id":31,"icon":25,"name":32,"slug":33},"26b0b636-0e31-4db1-bffb-61bdf9f20a58","Supply Chain","supply-chain",{"category":35},{"id":23,"icon":25,"name":26,"slug":27},{"category":37},{"id":38,"icon":25,"name":39,"slug":40},"e7b231c8-5f79-4465-8d38-1ef13aea5a14","Threat Intelligence","threat-intelligence",[42,46],{"type":43,"value":44,"context":45},"cve","CVE-2026-123710","Critical Red Hat Quay vulnerability",{"type":43,"value":47,"context":48},"CVE-2026-110697","Another Quay flaw mentioned",[21,18],{"controls":51,"vendors":139},[52,81,110],{"slug":53,"name":54,"problem":55,"products":56},"vulnerability-management","Vulnerability scanning and prioritisation","You know which systems are vulnerable, and which ones to fix first.",[57,65,73],{"vendor_slug":58,"vendor_name":59,"vendor_logo":60,"product_slug":61,"product_name":62,"url":63,"description":64},"holm-security","Holm Security","\u002Fvendor-logos\u002Fholm-security.png","holm-security-platform","Holm Security Platform","https:\u002F\u002Fwww.holmsecurity.com\u002F","Vulnerability scanning of systems, web applications, cloud and the external attack surface, plus phishing simulation.",{"vendor_slug":66,"vendor_name":67,"vendor_logo":68,"product_slug":69,"product_name":70,"url":71,"description":72},"axonius","Axonius","\u002Fvendor-logos\u002Faxonius.png","axonius-exposures","Axonius Exposures","https:\u002F\u002Fwww.axonius.com\u002Fplatform\u002Fexposures","Brings findings from different scanners together with asset and business context, to show what matters most and track fixes to the end.",{"vendor_slug":74,"vendor_name":75,"vendor_logo":76,"product_slug":77,"product_name":78,"url":79,"description":80},"tenable","Tenable","\u002Fvendor-logos\u002Ftenable.png","tenable-vulnerability-management","Tenable Vulnerability Management","https:\u002F\u002Fwww.tenable.com\u002Fproducts\u002Fvulnerability-management","Cloud-based vulnerability scanning and prioritisation, built on Nessus.",{"slug":82,"name":83,"problem":84,"products":85},"patch-management","Automated patch management","Known holes get closed in days, not months.",[86,94,102],{"vendor_slug":87,"vendor_name":88,"vendor_logo":89,"product_slug":90,"product_name":91,"url":92,"description":93},"manageengine","ManageEngine","\u002Fvendor-logos\u002Fmanageengine.png","patch-manager-plus","ManageEngine Patch Manager Plus","https:\u002F\u002Fwww.manageengine.com\u002Fpatch-management\u002F","Patch management for operating systems and third-party applications, on premises or in the cloud.",{"vendor_slug":95,"vendor_name":96,"vendor_logo":97,"product_slug":98,"product_name":99,"url":100,"description":101},"microsoft","Microsoft","\u002Fvendor-logos\u002Fmicrosoft.png","intune","Microsoft Intune","https:\u002F\u002Fwww.microsoft.com\u002Fen-us\u002Fsecurity\u002Fbusiness\u002Fmicrosoft-intune","Device management for Windows, macOS, iOS and Android, including update rings and compliance policies.",{"vendor_slug":103,"vendor_name":104,"vendor_logo":105,"product_slug":106,"product_name":107,"url":108,"description":109},"action1","Action1","\u002Fvendor-logos\u002Faction1.png","action1-patch-management","Action1 Patch Management","https:\u002F\u002Fwww.action1.com\u002F","Cloud-native patch management for Windows, macOS and third-party applications.",{"slug":111,"name":112,"problem":113,"products":114},"encryption-key-management","Encryption and key management","Stolen data stays unreadable, and the keys stay under your control.",[115,123,131],{"vendor_slug":116,"vendor_name":117,"vendor_logo":118,"product_slug":119,"product_name":120,"url":121,"description":122},"hashicorp","HashiCorp","\u002Fvendor-logos\u002Fhashicorp.png","vault","HashiCorp Vault","https:\u002F\u002Fwww.hashicorp.com\u002Fen\u002Fproducts\u002Fvault","Secrets management with short-lived credentials and encryption as a service.",{"vendor_slug":124,"vendor_name":125,"vendor_logo":126,"product_slug":127,"product_name":128,"url":129,"description":130},"thales","Thales","\u002Fvendor-logos\u002Fthales.png","luna-hsm","Thales Luna HSM","https:\u002F\u002Fcpl.thalesgroup.com\u002Fencryption\u002Fhardware-security-modules","Hardware security modules for protecting cryptographic keys.",{"vendor_slug":132,"vendor_name":133,"vendor_logo":134,"product_slug":135,"product_name":136,"url":137,"description":138},"utimaco","Utimaco","\u002Fvendor-logos\u002Futimaco.png","utimaco-hsm","Utimaco General Purpose HSM","https:\u002F\u002Futimaco.com\u002Fdata-protection\u002Fgp-hsm","Hardware security modules for key generation, storage and cryptographic operations.",[],{"slug":141,"title":142,"body":143,"framework_refs":144,"framework_notes":150},"unauthenticated-token-takeover-exposes-private-container-registries","Unauthenticated Token Takeover Exposes Private Container Registries","A critical flaw in Red Hat Quay allowed unauthenticated attackers to seize control of the registry's token-signing mechanism, granting themselves read\u002Fwrite access to any repository without valid credentials. This meant private container images, embedded secrets, and supply chain artifacts could be exfiltrated or silently overwritten, potentially poisoning downstream deployments. The vulnerability is especially dangerous because container registries sit at the heart of CI\u002FCD pipelines, making a single compromise a potential entry point into production environments. Organizations running Quay must treat key-management service exposure as a critical attack surface and act immediately while patches are finalized.",[145,146,147,148,149],"CIS Control 7: Continuous Vulnerability Management (v8)","NIST SP 800-53 IA-3: Device Identification and Authentication","NIST SP 800-53 SC-12: Cryptographic Key Establishment and Management","NIST CSF 2.0 PR.AA-05: Access permissions and authorizations","NIS2 Article 21(2)(e)",{"NIS2 Article 21(2)(e)":151,"CIS Control 7: Continuous Vulnerability Management (v8)":152,"NIST CSF 2.0 PR.AA-05: Access permissions and authorizations":153,"NIST SP 800-53 IA-3: Device Identification and Authentication":154,"NIST SP 800-53 SC-12: Cryptographic Key Establishment and Management":155},"This point covers vulnerability handling and disclosure in acquisition, development, and maintenance; a formal process for tracking and rapidly patching critical vulnerabilities in components like Quay is directly what this provision requires.","This control requires organisations to continuously assess and remediate vulnerabilities; applying the Quay patch promptly and tracking this critical CVE through a formal vulnerability management process would have directly limited exposure.","This category calls for restricting access to assets based on least privilege; limiting which services can reach the key-management endpoint would have blocked unauthenticated token takeover.","This control requires that systems authenticate before being granted access; enforcing authentication on the key-management service API would have prevented unauthenticated attackers from hijacking token signing.","This control mandates secure management of cryptographic keys; proper protection and access controls on Quay's signing keys would have prevented attackers from forging arbitrary tokens."]