CVE-2026-123710: Registry Token Signing Takeover in Red Hat Quay
- Vendor
- Red Hat
CVE-2026-123710 is a critical input-validation vulnerability in Red Hat Quay's service key server and key-rotation handler. The handler validates a bearer token's signature, audience, and issuer but does not verify that the token specifically authorizes service-key rotation. Because registry token issuance permits a caller-controlled audience, an ordinary registry token can satisfy these checks. An attacker can consequently install an attacker-controlled signing key that inherits approved status and has no expiration. Quay accepts registry tokens signed with this key for any repository, bypassing repository authorization. Anonymous token issuance permits unauthenticated exploitation; otherwise, a basic authenticated account is sufficient. The vulnerability affects Quay 3 and Quay 5 deployments, including standalone installations, Quay Operator deployments on OpenShift, and the mirror registry for Red Hat OpenShift. Its reported CVSS v3.1 score is 9.8.
Impact, mitigation & remediation
What it means and what to do now: patch path, interim mitigations, and the assume-compromise checklist.
Impact
What an attacker gets, and what they’ve been doing with it.
Successful exploitation compromises registry-wide confidentiality, integrity, and availability. Attackers can download private images across organizations and namespaces, potentially exposing embedded credentials and other secrets; push or overwrite images; and replace repository tags. Downstream workloads and CI/CD systems that retrieve modified images may suffer software supply-chain compromise. Malicious key rotation can delete legitimate instance signing keys, disrupting authorized image pulls and pushes. Attacker-installed keys can persist without expiry in the registry database across restarts and container upgrades, and are not invalidated by password resets or robot-account token changes.
Mitigation
If you can’t patch tonight, do this now.
Restrict the /keys service-key management endpoint at the proxy, ingress controller, or load balancer to trusted internal components only. Disable anonymous access to remove the unauthenticated exploitation path, but do not treat this as a complete mitigation because any valid account can still exploit the flaw. Review service_key_rotate and service_key_delete audit events, especially those with null expiration_date values, and inspect approved keys for unfamiliar identifiers or missing expiration timestamps. Remove unauthorized keys while maintaining access restrictions until a fixed build is deployed; key removal alone does not prevent reinsertion. Digest-pinned image references and enforced image-signature verification can reduce downstream exposure to malicious tag replacement.
Remediation
Patch, then assume compromise.
Upgrade every affected registry component to a vendor-confirmed fixed release. Reported fixed Quay 3 releases are 3.18.3, 3.17.7, 3.16.7, 3.15.9, 3.14.10, 3.12.24, 3.10.28, and 3.9.28 for their respective streams. Confirm applicability against current Red Hat advisories because the vulnerability records and release advisories contain inconsistent fix-status information; a fixed Quay 5 version is not identified in the available information. The upstream correction adds rotation-specific authorization bound to the replacement key, fixes registry-token audiences, rejects registry tokens for key-management operations, and enforces key expiration. Inspect persisted service keys and explicitly revoke unauthorized approved keys: upgrading containers alone does not remove keys already installed by an attacker. Restrict endpoint access before cleanup to prevent immediate reinsertion.
Exploits
No public exploits tracked yet. Mallory keeps watching.
Affected products & vendors
Products and vendors Mallory has correlated with this vulnerability. Open in Mallory to drill down to specific CPE configurations and version ranges.
References
Frequently asked questions
- Is CVE-2026-123710 exploited in the wild?
- As of Nov 17, 2026, Mallory has no reports of CVE-2026-123710 being exploited in the wild. It is not listed in CISA KEV.
- Is there a public exploit for CVE-2026-123710?
- As of Nov 17, 2026, Mallory has found no public exploit for CVE-2026-123710.
- Is there a patch for CVE-2026-123710?
- Upgrade every affected registry component to a vendor-confirmed fixed release. Reported fixed Quay 3 releases are 3.18.3, 3.17.7, 3.16.7, 3.15.9, 3.14.10, 3.12.24, 3.10.28, and 3.9.28 for their respective streams.
- What products are affected by CVE-2026-123710?
- Red Hat Quay.
- How severe is CVE-2026-123710?
- CVE-2026-123710 has a CVSS v3.1 score of 9.8 (Critical) and an EPSS score of 0.66% (52nd percentile) as of Nov 17, 2026.
Recent activity
41 sources tracked across advisories, community write-ups, and news. New activity surfaces here as Mallory finds it.