Red Hat Fixes Critical Quay Vulnerability Rated CVSS 9.8
The CVE-2026-123710 flaw in Red Hat Quay could allow unauthenticated takeover of registry token signing when the /keys interface is accessible.

The Red Hat Quay vulnerability identified as CVE-2026-123710 could allow an unauthenticated attacker to take over token signing for registries. Red Hat rates the flaw as critical, with a CVSS score of 9.8, and released a fix in the Red Hat Quay 3.15.9 update on November 11, 2026.
According to Red Hat, the accessible /keys interface is a prerequisite. The attack requires neither credentials nor user interaction. An attacker could gain the ability to sign registry tokens, which could then provide read and write permissions to private image repositories.
Red Hat Quay vulnerability and access to private images
The Quay container registry system is used to store and distribute container images. If CVE-2026-123710 is exploited, the created tokens could provide access to private repositories, including permission to modify their contents.
The risk also includes replacing image tags. A tag in a registry normally points to a specific version of a container image and is used in build or deployment processes. Manipulating a tag could therefore cause an automated process to download a different image than the one expected by its configuration.
In its advisory, Red Hat warns that the issue should be addressed particularly in external or insufficiently segmented deployments. There, access to the /keys interface could open a path to unauthorized reading and manipulation of private images. In the context of CI/CD, this represents a supply-chain risk because the registry is part of artifact distribution to build and deployment processes.
The fix is available in Red Hat Quay 3.15.9
Red Hat included CVE-2026-123710 in the critical Red Hat Quay 3.15.9 update released on November 11, 2026. Operators should identify Quay instances, verify their versions, and deploy the available fix.
Until the fixed version is deployed, Red Hat recommends restricting access to the /keys interface to trusted internal components only. This measure is intended to reduce exposure of the interface that, according to the flaw description, is critical to the unauthenticated takeover of token signing.
Organizations should also review audit records related to key rotation. The factual basis does not specify indicators of compromise or how to evaluate them, but reviewing the records follows directly from the vendor’s recommendation.
Active exploitation has not been confirmed
Available information does not confirm that the flaw has been exploited in real-world attacks. It has likewise not been confirmed that attackers added their own signing keys or used them to maintain access to the registry. Such a scenario is technically possible, but it is not described as a recorded incident.
Further developments will depend on the availability of fixes for other supported Quay versions and on any announcements from Red Hat, CISA, or security companies regarding active exploitation. The publication of more detailed technical information or public exploit code will also be important.
Sources
- Red Hat Customer Portal – CVE-2026-123710 – Confirms the mechanism for unauthenticated takeover of token signing, the Critical/CVSS 9.8 rating, and the recommended mitigation.
- Red Hat Security Advisory RHSA-2026:99023 – Confirms the release of the critical Red Hat Quay 3.15.9 update on November 11, 2026, and the inclusion of CVE-2026-123710.
- SecurityWeek – Independently summarizes the risk of exposing and overwriting private image repositories.
Verified and updated: November 12, 2026, 16:11



