CVE-2026-12573

waiting for further signalsZero needs more public information before it can validate it.

GHSA-jp8g-g3px-gw9c ↗EUVD-2026-120880 ↗

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.
Zohocorp DDI Central < 6201
fixed in 6201
CWE-77 Improper Neutralization of Special Elements used in a Command ('Command Injection')
ETK-2026-4051Zero's internal tracking ID, independent of the CVE number., permanent identifier
17h 32msince last run
1h 01mAI analysisAnalysis: how long the AI spent reversing this signal.
timeline
0 = cve.org publication
trigger signal (cve.org) +0hwaiting for further signals+2h05m
0
+4h
+6h
+8h
+10h
+12h

description

DDI Central build 6200 and earlier improperly handles DHCP pool names when managing Cisco routers. An authenticated attacker may cause commands to run on managed Cisco devices through this input.

mitigation

Upgrade DDI Central to build 6201 or later. Until upgraded, restrict access to authenticated DDI Central administration functions and limit management connectivity to Cisco routers.

fixed in 6201

check
no
exploit
no
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.
contextual
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
1h 01m
cve.org record, t = 0The moment cve.org publishes the CVE in full.
2026-11-10 11:22Z
Δ 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

Contextual, not validated: no deterministic check could cover this one, and no technique passed our review.

source signals

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

  1. 2026-11-10 11:22Z
    cve_org: trigger signal, started the run

this entry in the feed

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

{
  "etk_id": "ETK-2026-4051",
  "cve_id": "CVE-2026-12573",
  "display_id": "CVE-2026-12573",
  "ghsa_id": "GHSA-jp8g-g3px-gw9c",
  "euvd_id": "EUVD-2026-120880",
  "status": "published",
  "anchor_state": "anchored",
  "title": "Cisco IOS command injection in DDI Central",
  "summary": "DDI Central build 6200 and earlier improperly handles DHCP pool names when managing Cisco routers. An authenticated attacker may cause commands to run on managed Cisco devices through this input.",
  "mitigation": "Upgrade DDI Central to build 6201 or later. Until upgraded, restrict access to authenticated DDI Central administration functions and limit management connectivity to Cisco routers.",
  "vendor": "Zohocorp",
  "product": "DDI Central",
  "affected": [
    {
      "affected_notes": [],
      "affected_ranges": [
        ">= 0, < 6201"
      ],
      "ecosystem": null,
      "fixed_versions": [
        "6201"
      ],
      "package_name": "DDI Central",
      "purl": null
    }
  ],
  "cwes": [
    77
  ],
  "cvss_score": 8.8,
  "cvss_src": "cna_vendor",
  "cvss_vector": "CVSS:3.1/AV:N/AC:L/PR:L/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": 60.73080301666667,
  "t0_at": "2026-11-10T11:22:34.589000+00:00",
  "signals": {
    "trigger_signal": {
      "at": "2026-11-10T11:22:34.589000+00:00",
      "days": 0,
      "is_lower_bound": false,
      "measured_at": "2026-11-10T11:22:34.589000+00:00",
      "url": "https://www.cve.org/CVERecord?id=CVE-2026-12573"
    }
  }
}

published 2026-11-10 11:48Z
last change 2026-11-11 06:34Z

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.