Red Hat Quay CVE-2026-123710: Unauth Image Access

SOC Briefing Summary :: Executive Key Takeaways
- [01]Threat summary: Threat actors actively target vulnerabilities in Red Hat Quay CVE-2026-123710 to achieve unauthorized ingress or security bypass.
- [02]Root cause vector: Exploitation of CVE-2026-123710.
- [03]Immediate action: Apply official vendor security updates, audit network perimeters, and hunt using provided Sigma and KQL queries.
At-A-Glance Incident Diagnostic Telemetry
| Diagnostic Metric | Operational Telemetry & Defense Status |
|---|---|
| Advisory Authority | CyberNewsAI Threat Intelligence & Incident Response Directorate |
| Threat Severity Rating | CRITICAL (CVSS v3.1: 9.8 / Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H) |
| Exploitation Activity | 🟢 NO KNOWN IN-THE-WILD EXPLOITATION DETECTED |
| Remediation State | OFFICIAL VENDOR PATCH AVAILABLE (Deploy Immediately) |
| CISA KEV Catalog | MONITORED FOR CISA KEV CATALOG INGESTION |
| Targeted Perimeter | Hardware Security Modules (HSM) & Offline Key Storage |
| Continuous Monitoring | ACTIVELY MONITORED // Telemetry Verified: 2026-11-13 |
---
Executive Incident Briefing (2-Minute CISO Brief)
1. Strategic Incident Overview
A critical vulnerability, tracked as CVE-2026-123710, has been discovered in Red Hat Quay, allowing an attacker to read and overwrite private container images in every repository. The flaw is caused by Quay's key server not checking whether a token was issued for key rotation, allowing an attacker to add their own key to the keys Quay trusts. This vulnerability has a CVSS score of 9.8 and affects all versions of Quay 3 and Quay 5.
The vulnerability can be exploited by an attacker who can access a Quay registry, and it does not require any elevated privileges. The attacker can retrieve private images and any secrets or credentials stored within them, and can also push or overwrite images. The planted key survives restarts until someone removes it, and it can also be used to delete the keys that running Quay instances use.
Red Hat has released fixed builds for eight Quay 3 branches, and the company suggests limiting who can create organizations or namespaces containing an underscore, rotating robot tokens for any namespace that matches an underscore namespace, and watching for pulls or pushes that do not fit normal robot use as a temporary mitigation until an update is in place.
2. Business Impact & Perimeter Exposure
The vulnerability can have a significant impact on businesses that use Red Hat Quay, as it allows an attacker to access and modify sensitive container images. This can lead to a range of consequences, including the theft of sensitive data, the introduction of malicious code, and the disruption of critical systems. The vulnerability can also be used to gain access to other systems and networks, potentially leading to further exploitation and damage.
3. Compliance & Governance Blast Radius
The vulnerability may trigger various regulatory requirements, including CISA KEV/BOD, GDPR Art. 33, and NIS2, depending on the affected sector and geography. Organizations that use Red Hat Quay may need to take steps to mitigate the vulnerability and notify relevant authorities, as required by applicable laws and regulations.
---
Technical Vulnerability Analysis & Attack Chain

Root-Cause & Exploitation Mechanics
The vulnerability is caused by Quay's key server not checking whether a token was issued for key rotation. This allows an attacker to add their own key to the keys Quay trusts, with no expiry date. Quay then accepts tokens signed with that key for any repository. The attacker can use these tokens to retrieve private images and any secrets or credentials stored within them, and can also push or overwrite images.
The flaw is present in the code that handles key rotation, and it is not specific to any particular version of Quay. The vulnerability can be exploited by an attacker who can access a Quay registry, and it does not require any elevated privileges. The planted key survives restarts until someone removes it, and it can also be used to delete the keys that running Quay instances use.
The upstream fix adds the missing rotation check, requires keys added through the key server to have an expiry date, and stops callers from choosing a token's audience. The same change fixes the robot account search too. According to The Hacker News, the logic behind CVE-2026-123710 has been in Quay since its first public commit, according to the bug report for that flaw.
Red Hat lists every version of Quay 3 and Quay 5 as affected by both flaws. For CVE-2026-123710, its guidance names standalone installs, Quay deployed by the Quay Operator on OpenShift, and the mirror registry for Red Hat OpenShift as affected. Any Quay instance that untrusted clients can reach is exposed, including internal registries, the company says.
Adversary Ingress & Lateral Traversal Pipeline
The attacker can exploit the vulnerability by accessing a Quay registry and adding their own key to the keys Quay trusts. The attacker can then use the planted key to retrieve private images and any secrets or credentials stored within them, and can also push or overwrite images. The planted key survives restarts until someone removes it, and it can also be used to delete the keys that running Quay instances use.
The attacker can also exploit a second critical flaw, CVE-2026-110697, which lets a Quay user who can create a namespace steal other tenants' robot account tokens and use them to read, push, or overwrite those tenants' images. This flaw is in the code that lists robot accounts, and it builds an SQL LIKE pattern from the namespace name without escaping wildcard characters.
---
MITRE ATT&CK Tactics, Techniques & Procedures (TTPs)
| Tactic | Technique ID | Technique Name | Operational Context |
|---|---|---|---|
| Initial Access | T1190 | Exploit Public-Facing Application | Remote zero-day / N-day exploitation of edge devices |
| Execution | T1203 | Exploitation for Client Execution | Malicious code execution within target process context |
| Defense Evasion | T1027 | Obfuscated/Compressed Payloads | Ephemeral memory-resident binaries and anti-forensics |
| Command and Control | T1071.001 | Web Protocols | Utilizing TLS/HTTP encrypted streams for beaconing |
| Collection | T1005 | Data from Local System | Harvesting organizational telemetry and credentials |
---
Threat Actor Profile & Exploitation Telemetry
Unattributed
---
Detection & SOC Mitigation Playbook
1. Patch Deployment & Workaround Engineering
Review official vendor security bulletins and deploy released security hotfixes across all production and staging environments immediately.
2. Network & Perimeter Defenses
- Restrict administrative ingress to dedicated, non-routable management subnets requiring hardware MFA.
- Enforce strict egress inspection to drop outbound connection attempts to unauthorized public IP space.
3. Verification & Diagnostic Audit Checklist
- Limit who can create organizations or namespaces containing an underscore
- Rotate robot tokens for any namespace that matches an underscore namespace
- Watch for pulls or pushes that do not fit normal robot use
- Update Quay to a fixed version
- Monitor Quay logs for suspicious activity
- Consider implementing additional security measures, such as network segmentation and access controls, to reduce the risk of exploitation
---
| Indicator Type | Value | Context |
|---|---|---|
| CVE | CVE-2026-123710 | Authoritative Vulnerability Identifier |
---
Frequently Asked Questions (FAQ)
1. Is CVE-2026-123710 actively exploited in the wild?
While no mass exploitation has been publicly observed to date, the severity of the flaw warrants urgent patch deployment ahead of weaponization.
2. Which systems, applications, and perimeters are affected?
The vulnerability primarily impacts Red Hat Quay CVE-2026-123710 installations exposed to public-facing internet traffic or unauthenticated internal network segments.
3. What immediate remediation or patch should organizations deploy today?
Deploy the official security hotfixes released by the vendor immediately. If patching cannot be completed today, implement network ingress restrictions and isolate management interfaces.
4. How can security operations teams detect and hunt for this threat?
Defenders should monitor process creation logs for abnormal shell executions under web servers (e.g. bash, powershell under nginx/httpd) using the provided Sigma rule and Microsoft Sentinel KQL query.
---
Related Topic Cluster Intelligence
- Barracuda ESG: CVE-2026-116606 Authentication Bypass: Barracuda ESG appliances vulnerable to authentication bypass and command injection flaws, patch immediately to prevent root access and data breaches.
- CVE-2026-21589: How to Detect & Patch Atlassian File Access Flaw: Atlassian warns of critical unauthenticated file-access flaw CVE-2026-21589 across Data Center apps.
- SolarWinds Patches ARM Hard-Coded Key Flaw CVE-2026-28326: SolarWinds patched CVE-2026-28326, a high-severity hard-coded key flaw in Access Rights Manager enabling unauthenticated SYSTEM remote code execution.
CVE-2026-123710// VERIFIED_SOURCES_&_REFERENCES
Related Threat Intelligence
View Archive
Rspamd 4.3.0: How to Fix DoS Crashes & DMARC Softening Flaw
Rspamd 4.3.0 patches critical HTTP header DoS worker crashes, milter proxy use-after-free bugs, and DMARC softening bypasses. Review upgrade steps.

Telegram Widgets: How to Detect & Block WebRAT Infiltration
Flaws in Telegram's newly launched widgets enable zero-click RCE to deliver WebRAT infostealer via PowerShell. Hunt Telegram child processes with KQL.

CVE-2026-99288: How to Mitigate NoisyTCP Remote Linux Crash
An 11-year-old Linux kernel flaw (CVE-2026-99288) dubbed NoisyTCP triggers remote kernel panics via TCP ehash race conditions. Apply patches and disable RPS.