One Quay flaw lets attackers sign their own registry tokens. Password resets won't help.
By Lior AharonovFounder, 7IT Solutions ·
What happened
Red Hat disclosed CVE-2026-123710, rated CVSS 9.8, in its Quay container registry, SecurityWeek reported on 12 November. Any valid Quay account, or no account where anonymous access is on, can install a trusted signing key through the service key server and issue tokens with read and write access to any repository. Fixes were merged into the Quay code on 11 November.
Why it matters
Your private images, and any secrets inside them, become readable. Worse, an attacker can overwrite the images your servers pull next, and the planted key survives restarts.
What to do
If you run Red Hat Quay, block untrusted clients from the service key server today, review logs for key changes and delete any key you did not create. Changing passwords or robot tokens does not remove it.

My take
Lior Aharonov
Founder, 7IT Solutions
Your registry is the last stop before production. Whoever signs its tokens decides what you ship.
Sources
| SecurityWeek: Critical Red Hat Quay Vulnerability Could Expose Private Container Images | securityweek.com |
Researched with AI tools; every fact is checked against the linked sources.