CVE-2026-123710
waiting for further signalsZero needs more public information before it can validate it.GHSA-jw94-v4wp-236w ↗EUVD-2026-123542 ↗
description
Red Hat Quay 3 has an authorization flaw in its registry signing-key rotation handling. A remote unauthenticated attacker able to reach an affected service and obtain an anonymous registry token may cause the registry to trust an attacker-controlled signing key, enabling access to private images and modification of repository tags.
mitigation
Immediately restrict unauthenticated network access to affected Quay instances, especially the key-rotation service endpoint, using network controls. Audit for unauthorized signing keys and repository tag changes, rotate affected signing keys, and apply vendor remediation when it becomes available.
outcome
No artifact: an exploit or check was attempted but could not be produced at this moment.
source signals
Public signals that triggered or updated the pipeline. These are inputs for the deltas above.
- 2026-11-11 15:02Zcve_org: trigger signal, started the run
this entry in the feed
GET /api/v1/feed/CVE-2026-123710
{ "etk_id": "ETK-2026-4180", "cve_id": "CVE-2026-123710", "display_id": "CVE-2026-123710", "ghsa_id": "GHSA-jw94-v4wp-236w", "euvd_id": "EUVD-2026-123542", "status": "published", "anchor_state": "anchored", "title": "Authorization bypass in Quay registry key rotation", "summary": "Red Hat Quay 3 has an authorization flaw in its registry signing-key rotation handling. A remote unauthenticated attacker able to reach an affected service and obtain an anonymous registry token may cause the registry to trust an attacker-controlled signing key, enabling access to private images and modification of repository tags.", "mitigation": "Immediately restrict unauthenticated network access to affected Quay instances, especially the key-rotation service endpoint, using network controls. Audit for unauthorized signing keys and repository tag changes, rotate affected signing keys, and apply vendor remediation when it becomes available.", "vendor": "Red Hat", "product": "Red Hat Quay 3", "affected": [ { "affected_notes": [], "affected_ranges": [], "ecosystem": null, "fixed_versions": [], "package_name": "quay/quay-rhel8", "purl": null }, { "affected_notes": [], "affected_ranges": [], "ecosystem": null, "fixed_versions": [], "package_name": "quay/quay-rhel9", "purl": null } ], "cwes": [ 1287 ], "cvss_score": 9.8, "cvss_src": "cna_vendor", "cvss_vector": "CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H", "epss_score": null, "epss_percentile": null, "epss_asof": null, "automation": "deterministic", "check": false, "check_confidence_basis": null, "exploit": false, "pipeline_minutes": 27.334727283333333, "t0_at": "2026-11-11T15:02:31.341000+00:00", "signals": { "trigger_signal": { "at": "2026-11-11T15:02:31.341000+00:00", "days": 0, "is_lower_bound": false, "measured_at": "2026-11-11T15:02:31.341000+00:00", "url": "https://www.cve.org/CVERecord?id=CVE-2026-123710" } } }
published 2026-11-11 15:27Z
last change 2026-11-11 19:02Z
Need the technical details behind an entry?
Every entry here shows what we attempted and when. The technical details, the generated exploit that fired it and the evidence behind the verdict are not public. Tell us about your use case and we’ll get back to you about extended API access.