Red Hat disclosed CVE-2026-123710 on November 11, 2026. The Quay flaw can allow a rogue signing key to be installed, opening access to private container images. Teams delivering applications through Quay need to inspect signing keys as well as passwords.
A registry can accept an unauthorized key
Red Hat describes insufficient validation of tokens presented to the key rotation service. An anonymous registry token can be accepted for a role it was not intended to perform. A newly approved key can then sign tokens granting repository access.
The exposure to check is whether untrusted clients can reach the key service. This concerns the authority that validates registry access, beyond an individual developer’s password.
Private images and their tags are at risk
Cyber Security News explains the missing separation between a registry token and permission to rotate keys. Its analysis also highlights replacement of image tags: a build system may later retrieve unexpected content through its usual reference.
We recommend listing applications that pull images from the affected Quay deployment. A familiar image tag is insufficient evidence that its contents have remained unchanged.
Ordinary credential rotation has limits
SecurityWeek notes that a malicious key can survive restarts, and that changing passwords or regenerating robot tokens does not invalidate it. Turning off anonymous access is also insufficient if a valid account can reach the vulnerable service.
This changes what to request from an IT provider: ask which categories of keys were inspected. A list of changed passwords does not address a compromised signing authority.
Restrict, investigate and deploy a vendor fix
Red Hat advises restricting /keys to trusted internal components, reviewing suspicious service_key_rotate and service_key_delete events and removing unrecognized approved keys. Without a fix, a deleted rogue key can be installed again.
In its November 12 report, SecurityWeek noted that the cited advisories did not identify a fixed version despite merged source changes. Check the vendor status for your own release. We also recommend validating images consumed during the suspect period and assessing secrets potentially stored in them before deliveries resume.
The connection with Soclyde
Quay shows why incident responders must distinguish signing keys, robot tokens and human passwords. Soclyde helps keep administrators’ unique passwords in an encrypted local vault. It does not verify Quay signatures or remove unauthorized registry keys.
What to remember
Restrict key-service exposure, have approved keys examined and confirm the vendor fix. Prepare separate replacement passwords for human accounts with our password generator.



