Skip to main content
Mallory
CriticalVulnerability

CVE-2026-123710: Registry Token Signing Takeover in Red Hat Quay

Published Nov 11, 2026 · Updated today
Trending this week#23of 428,812 vulnerabilities
Mention activity · 30 days41 mentions · peak 13 in a dayToday
CVSS9.8Critical · v3.1
EPSS0.66%52nd percentile
CISA KEVNoNot listed
In the wildNoneNo exploitation reported
Vendor
Red Hat
IdentifiersCVE-2026-123710CWE-1287 · Improper Validation of Specified…

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.

Do you run this?See affected versions in your environment and whether adversaries are exploiting this vulnerability against assets like yours.
Check your exposure
Analyst brief

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.

Public exploits

Exploits

No public exploits tracked yet. Mallory keeps watching.

View more in app →
No public exploit code observed for this vulnerability. Mallory keeps watching.
Exposure surface

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.

VendorProductType
Red HatQuayapplication
FAQ

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.
Activity feed

Recent activity

41 sources tracked across advisories, community write-ups, and news. New activity surfaces here as Mallory finds it.

View more in app →
uganda certNews · Nov 17, 2026Red Hat Quay Flaws Allow Registry-Wide Access to Every Private Container Image (CVE-2026-123710 / CVE-2026-110697) | Uganda National Computer Emergency Response Team-National CertA critical authorization flaw in Red Hat Quay, rated CVSS 9.8, permits registry-wide reading and overwriting of private container images. Exploitation requires no account when anonymous access is enabled, which is allowed by default; otherwise, any valid account suffices. The vulnerable logic reportedly dates to Quay’s first public commit. Unauthorized image modification presents a downstream software supply-chain risk.Read more ↗sh3llc0d3 blogNews · Nov 14, 2026Critical Red Hat Quay Signing-Key Takeover | ShellcodeCritical JWT signing-key injection vulnerability in Red Hat Quay, reported with CVSS 9.8. An attacker can use an ordinary registry token to register an attacker-controlled, non-expiring signing key. Exploitation is unauthenticated when anonymous /v2/auth token issuance is enabled; otherwise, basic authentication is required. The trusted key enables arbitrary repository read/write access and deletion of legitimate signing keys, potentially exposing secrets, compromising downstream container deployments, or disrupting registry authentication. Implanted keys persist in the database across restarts and upgrades, requiring auditing and revocation in addition to patching.Read more ↗cysecurity newsNews · Nov 13, 2026Critical Red Hat Quay Flaw Could Allow Attackers to Steal Private Container Images - CySecurity News - Latest Information Security and Hacking IncidentsA critical vulnerability in Red Hat Quay's service key server, rated CVSS 9.8, allows attackers to manipulate signing-key rotation and install a trusted malicious key when the service is accessible to untrusted clients. With anonymous access enabled, exploitation requires no authentication; otherwise, valid Quay users can still exploit it. Attackers can forge registry tokens to read private images, overwrite repositories, expose embedded secrets, and delete legitimate signing keys. Malicious keys can persist across registry restarts without expiration, and password changes or robot-token regeneration do not revoke them. Administrators should immediately restrict access to the key-management service. Fixes were merged into the project repository on November 11, but the content does not confirm availability of a released fixed version.Read more ↗hawkeye blogNews · Nov 13, 2026Weekly Threat Landscape Digest - Week 46 - HawkEyeA CVSS 9.8 authorization vulnerability in Red Hat Quay permits anonymous-token abuse to register attacker-controlled signing keys with indefinite approval. Attackers can forge registry tokens, access private images, and replace tags. Only deployments exposing /keys to untrusted clients are vulnerable; no patch is available.Read more ↗
+10 more in the timeline. Sign up to see them
Do you run this?See affected versions in your environment and whether adversaries are exploiting this vulnerability against assets like yours.
Check your exposure
Mallory platform

The version that knows your environment.

This page is what’s public. Mallory adds the parts that aren’t: which of your assets are affected, which adversaries are exploiting it right now, and which detections to deploy tonight.
Exposure mappingQuery your assets running an affected version, and investigate the blast radius.
Threat actor evidenceEvery report linking this CVE to a named adversary.
Associated malwareMalware families linked to this CVE, with evidence and IOCs.
Detection signaturesYARA, Sigma, Snort, and vendor rules, auto-deployed to your SIEM.
Vendor-by-vendor mappingCross-references every affected SKU, including bundled OEM variants.
Social activity26Community discussion across Reddit, Mastodon, and other social sources.