Quay: red hat quay: unauthenticated registry signing-key takeover via service key rotation
Workaround:the vendor lists a workaround. No fixed version in the CVE record. See workaround ↓
Project Quay · quay
A flaw in the service key rotation component of Project Quay's Red Hat Quay registry lets an unauthenticated client obtain an anonymous registry token with an audience it controls and use it to install its own signing key, with no expiry. An attacker needs only network access to the registry and no credentials or user interaction; once their key is accepted, tokens they sign are honoured for any repository, giving read and write access to private images and the ability to replace repository tags.
Official description · NVD
A flaw was found in Red Hat Quay. An unauthenticated client can obtain an anonymous registry token with an audience it controls, present that token to the service key rotation endpoint, and install its own approved signing key with no expiry. Registry tokens signed with that key are accepted for any repository, allowing read and write access to private images and replacement of repository tags.
- Exploited
- Not confirmed
- Reports
- 0
- Tactics
- 0/15
Exploitation timelineDated milestones for a CVE: when it was disclosed, when exploit code became public, when exploitation was confirmed, and when threat reports named it.
Disclosed on 11 Nov 2026. No public exploit code or confirmed exploitation is recorded.
Affected versions and fixes
as published in the CVE recordProject Quay quay
Affected: < 3.9.28 · >= 3.10.0, < 3.10.28 · >= 3.12.0, < 3.12.24 · >= 3.14.0, < 3.14.10 · >= 3.15.0, < 3.15.9 · >= 3.16.0, < 3.16.7 · >= 3.17.0, < 3.17.7 · >= 3.18.0, < 3.18.3
Red Hat mirror registry for Red Hat OpenShift 2.0
Affected: all versions
Red Hat Red Hat Quay 3.10
Affected: all versions
Red Hat Red Hat Quay 3.12
Affected: all versions
Red Hat Red Hat Quay 3.14
Affected: all versions
Red Hat Red Hat Quay 3.15
Affected: all versions
Red Hat Red Hat Quay 3.16
Affected: all versions
Red Hat Red Hat Quay 3.17
Affected: all versions
Red Hat Red Hat Quay 3.18
Affected: all versions
Red Hat Red Hat Quay 3.9
Affected: all versions
Workaround
Restrict access to the /keys endpoint at the proxy or load balancer so only trusted internal components can reach it. Review audit logs for service_key_rotate and service_key_delete events with a null expiration_date, and remove any unrecognised approved service keys. Deleting a rogue key is not durable until a fixed build is deployed, because the anonymous request can install a new key.
What security researchers reported
Not named in any threat report yetAlso mentioned in 8 community threat pulses (AlienVault OTX)
Weaker evidencePulses are indicator collections that anyone can publish. A mention is not confirmation of exploitation.
- Known_Cve | Nov 20, 2026 | Part 1/319 Nov 2026
- Known_Cve | Nov 19, 2026 | Part 1/319 Nov 2026
- Known_Cve | Nov 18, 2026 | Part 2/317 Nov 2026
- Known_Cve | Nov 17, 2026 | Part 2/316 Nov 2026
- Known_Cve | Nov 16, 2026 | Part 2/315 Nov 2026
- Known_Cve | Nov 15, 2026 | Part 3/314 Nov 2026
- 2 more on OTX