CVE-2026-123710

validatingZero is analyzing and reversing it now.

GHSA-jw94-v4wp-236w ↗

no check availablenot proven exploitable
cve.orgpublic pocExploit code has been published by someone. Source signals can also carry a PoC (Proof of Concept).kevAttacks confirmed in the real world.
Red Hat Quay 3
CWE-1287 Improper Validation of Specified Type of Input
ETK-2026-4180Zero's internal tracking ID, independent of the CVE number., permanent identifier
–running
startingcurrent stage
timeline
0 = trigger signal
trigger signal (cve.org) +0h
0
+2h
+4h
+6h
+8h
+10h
+12h

description

Red Hat Quay 3 can allow an unauthenticated client to install an approved registry signing key through the service key-rotation endpoint. An attacker could then use tokens signed with that key to read and modify private images and replace repository tags, if the affected service is reachable without authentication.

Still under analysis: more detail becomes available as the pipeline runs.

mitigation

Restrict access to Quay and its service key-rotation endpoint to trusted administrative networks and identities. Monitor for unexpected signing-key, private-image, and tag changes, and apply a vendor-provided fixed release when one is available.

check
building now
exploit
not yet
automationDeterministic: a check that runs on its own, the same request on every target. Contextual: an agentic technique that needs to be applied per target, for bugs that depend on contextual flows.
–
auth requiredWhether an attacker needs an account first, based on the CVSS vector's Privileges Required.
no
EPSSEstimate of the chance this CVE is exploited in the next 30 days. Refreshed daily.
–
agent run time
29m
cve.org record, t = 0The moment cve.org publishes the CVE in full.
2026-11-11 15:02Z
Δ to public pocExploit code has been published by someone. Source signals can also carry a PoC (Proof of Concept).
–
Δ to kevAttacks confirmed in the real world.
–

outcome

Run in progress: no artifact yet.

source signals

Public signals that triggered or updated the pipeline. These are inputs for the deltas above.

  1. 2026-11-11 15:02Z
    cve_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": null,
  "status": "in_pipeline",
  "anchor_state": "anchored",
  "title": "Unauthenticated signing-key installation in Red Hat Quay",
  "summary": "Red Hat Quay 3 can allow an unauthenticated client to install an approved registry signing key through the service key-rotation endpoint. An attacker could then use tokens signed with that key to read and modify private images and replace repository tags, if the affected service is reachable without authentication.",
  "mitigation": "Restrict access to Quay and its service key-rotation endpoint to trusted administrative networks and identities. Monitor for unexpected signing-key, private-image, and tag changes, and apply a vendor-provided fixed release when one is 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": "contextual",
  "check": false,
  "check_confidence_basis": null,
  "exploit": false,
  "pipeline_minutes": 28.957974566666667,
  "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 15:57Z

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.