CVE-2026-110697

validatingZero is analyzing and reversing it now.
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 OpenShift Update Service
CWE-89 Improper Neutralization of Special Elements used in an SQL Command ('SQL Injection')
ETK-2026-4196Zero'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

Quay's robot-account listing can interpret wildcard characters in user-controlled namespace names as database pattern syntax. An attacker who can create a namespace with an underscore may obtain robot-account credentials from other tenants and use them for unauthorized image-related actions.

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

mitigation

Restrict namespace creation to trusted users and enforce a namespace naming policy that rejects underscore characters until an updated Quay package is available. Apply the vendor-provided fixed release when it is published.

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.
yes, low privileges
EPSSEstimate of the chance this CVE is exploited in the next 30 days. Refreshed daily.
–
agent run time
–
cve.org record, t = 0The moment cve.org publishes the CVE in full.
2026-11-11 17:06Z
Δ 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 17:06Z
    cve_org: trigger signal, started the run

this entry in the feed

GET /api/v1/feed/CVE-2026-110697

{
  "etk_id": "ETK-2026-4196",
  "cve_id": "CVE-2026-110697",
  "display_id": "CVE-2026-110697",
  "ghsa_id": null,
  "euvd_id": null,
  "status": "in_pipeline",
  "anchor_state": "anchored",
  "title": "Cross-tenant credential exposure in Quay robot account listing",
  "summary": "Quay's robot-account listing can interpret wildcard characters in user-controlled namespace names as database pattern syntax. An attacker who can create a namespace with an underscore may obtain robot-account credentials from other tenants and use them for unauthorized image-related actions.",
  "mitigation": "Restrict namespace creation to trusted users and enforce a namespace naming policy that rejects underscore characters until an updated Quay package is available. Apply the vendor-provided fixed release when it is published.",
  "vendor": "Red Hat",
  "product": "Red Hat OpenShift Update Service",
  "affected": [
    {
      "affected_notes": [],
      "affected_ranges": [],
      "ecosystem": null,
      "fixed_versions": [],
      "package_name": "openshift-update-service/openshift-update-service-rhel8",
      "purl": null
    },
    {
      "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": [
    89
  ],
  "cvss_score": 9.9,
  "cvss_src": "cna_vendor",
  "cvss_vector": "CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:H/A:H",
  "epss_score": null,
  "epss_percentile": null,
  "epss_asof": null,
  "automation": null,
  "check": false,
  "check_confidence_basis": null,
  "exploit": false,
  "pipeline_minutes": null,
  "t0_at": "2026-11-11T17:06:13.261000+00:00",
  "signals": {
    "trigger_signal": {
      "at": "2026-11-11T17:06:13.261000+00:00",
      "days": 0,
      "is_lower_bound": false,
      "measured_at": "2026-11-11T17:06:13.261000+00:00",
      "url": "https://www.cve.org/CVERecord?id=CVE-2026-110697"
    }
  }
}

published 2026-11-11 17:36Z
last change 2026-11-11 17:55Z

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.