[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"$fIqwxojnww7JZOVSCD_g4VGv4kFmVzW5t73flb4qDBtE":3},{"lesson":4},{"id":5,"slug":6,"article_id":7,"title":8,"body":9,"prevention":10,"framework_refs":11,"framework_notes":17,"status":23,"created_at":24,"published_at":25,"article":26,"tags":30,"podcasts":49,"controls":56},"0300f1c2-7745-4b1c-b875-6b597256f38c","misconfigured-anonymous-access-exposes-container-registries-to-full-hijack","bdfe6e6f-5d5b-4d5e-abe4-21b38e067bf3","Misconfigured Anonymous Access Exposes Container Registries to Full Hijack","A critical flaw in Red Hat Quay (CVE-2026-123710, CVSS 9.8) demonstrates how a permissive default feature flag—FEATURE_ANONYMOUS_ACCESS—combined with an unprotected cryptographic endpoint can hand attackers the keys to an entire container registry. By injecting malicious signing keys via the \u002Fkeys endpoint, unauthenticated adversaries can gain read\u002Fwrite control over private images and manipulate repository tags, poisoning any downstream software built from those images. This matters far beyond the registry itself: compromised container images propagate silently into CI\u002FCD pipelines, production deployments, and customer environments. The incident underscores that cryptographic trust mechanisms are only as strong as the access controls protecting them.","**Immediate actions:**\n- Block unauthenticated access to the \u002Fkeys endpoint at the proxy or load balancer layer until a patched Quay version is available.\n- Audit all registered service keys in your Quay instance and revoke any that cannot be positively verified as legitimate.\n- Disable FEATURE_ANONYMOUS_ACCESS unless there is an explicit, documented business requirement for it.\n\n**Long-term improvements:**\n- Establish a hardened baseline configuration for all container registry deployments and enforce it through infrastructure-as-code and automated compliance checks.\n- Integrate container image signing verification (e.g., Sigstore\u002FCosign) into every CI\u002FCD pipeline so tampered images are rejected before deployment.\n- Apply the principle of least privilege to all registry API endpoints, requiring authentication and role-based authorization for any operation that reads or writes cryptographic material.\n\n**Detection measures:**\n- Enable detailed audit logging on the \u002Fkeys endpoint and alert on any key registration or modification event originating from an unauthenticated or unexpected source.\n- Deploy continuous vulnerability scanning against container registry infrastructure to surface critical CVEs within hours of disclosure.\n- Monitor image tag mutation events and alert on unexpected tag reassignments, which are a key indicator of supply-chain tampering.",[12,13,14,15,16],"CIS Control 4: Secure Configuration of Enterprise Assets and Software","NIST SP 800-53 AC-3: Access Enforcement","NIST SP 800-53 SC-12: Cryptographic Key Establishment and Management","NIS2 Article 21(2)(d)","MITRE ATT&CK T1553.002: Subvert Trust Controls: Code Signing",{"NIS2 Article 21(2)(d)":18,"NIST SP 800-53 AC-3: Access Enforcement":19,"MITRE ATT&CK T1553.002: Subvert Trust Controls: Code Signing":20,"NIST SP 800-53 SC-12: Cryptographic Key Establishment and Management":21,"CIS Control 4: Secure Configuration of Enterprise Assets and Software":22},"This point requires security measures addressing supply chain risks; the ability to swap container image tags and inject malicious images into downstream pipelines is precisely the supply-chain attack scenario NIS2 Article 21(2)(d) is designed to prevent.","AC-3 requires that the system enforce approved authorizations for all access to resources; enforcing authentication before allowing any interaction with the cryptographic \u002Fkeys endpoint would have prevented unauthenticated key injection.","This technique describes adversaries undermining code-signing mechanisms to make malicious artifacts appear legitimate, which is exactly what injecting rogue signing keys into the Quay \u002Fkeys endpoint achieves.","SC-12 requires protecting cryptographic keys throughout their lifecycle; controlling who can register or modify signing keys is a direct requirement of this control that was violated by the exposed \u002Fkeys endpoint.","This control requires establishing and maintaining secure configurations; disabling FEATURE_ANONYMOUS_ACCESS and restricting the \u002Fkeys endpoint to authenticated callers is exactly the kind of hardened baseline it mandates.","published","2026-11-12T14:20:21.984534+00:00","2026-11-12T14:20:21.972+00:00",{"id":7,"url":27,"slug":28,"title":29},"https:\u002F\u002Fcybersecuritynews.com\u002Fred-hat-quay-vulnerability\u002F","critical-red-hat-quay-vulnerability-allows-unauthenticated-attackers-to-hijack-c-06455e","Critical Red Hat Quay Vulnerability Allows Unauthenticated Attackers to Hijack Container Registries",[31,37,43],{"id":32,"name":33,"slug":34,"description":35,"color":36},"1ec88fde-2d0f-4ed8-932a-33f5ccc0fdc7","Access Control","access-control","Excessive privileges, missing MFA, weak auth","#f97316",{"id":38,"name":39,"slug":40,"description":41,"color":42},"859cf0ad-a7e9-42bb-a75d-bac6511fa5d5","Configuration Management","configuration-management","Misconfigs, default credentials, exposed services","#eab308",{"id":44,"name":45,"slug":46,"description":47,"color":48},"f0c2a0af-58aa-4128-87c9-6acd30f2dc48","Supply Chain","supply-chain","Third-party risk, compromised dependencies","#8b5cf6",[50],{"id":51,"date":52,"edition":53,"title":54,"audio_url":55},"636c0875-eb3c-4df8-b0a8-59b022d18a1e","2026-11-12","afternoon","ThreatNoir Afternoon Brief — November 12","https:\u002F\u002Fcdn.threatnoir.com\u002Fpodcasts\u002F2026-11-12\u002Fthreatnoir-afternoon-brief-2026-11-12.mp3",[57,61,65],{"slug":58,"name":59,"problem":60},"identity-threat-detection","Identity threat detection and response (ITDR)","Attackers who log in with real, stolen credentials get noticed.",{"slug":62,"name":63,"problem":64},"patch-management","Automated patch management","Known holes get closed in days, not months.",{"slug":66,"name":67,"problem":68},"network-segmentation","Network segmentation and microsegmentation","One compromised machine can no longer reach everything else."]