← back to feed
CVE-2026-114625

CVE-2026-114625

waiting for further signalsZero needs more public information before it can validate it.
no check availablenot proven exploitable
awaiting cvepublic pocExploit code has been published by someone. Source signals can also carry a PoC (Proof of Concept).kevAttacks confirmed in the real world.
VeloCloud Orchestrator
ETK-2026-2470Zero's internal tracking ID, independent of the CVE number., permanent identifier
cvss9.0ethiack provisional
1h 49msince last run
6mAI analysisAnalysis: how long the AI spent reversing this signal.
timeline
0 = cve.org, not yet published
trigger signal −2h02mwaiting for further signals−1h49m
−2h
−1h
0

description

Security updates are available for an actively exploited zero-day affecting VeloCloud Orchestrator. The available evidence does not specify the vulnerability class, affected function, attacker impact, or conditions needed for exploitation.

mitigation

Apply the vendor security updates for VeloCloud Orchestrator promptly. Restrict access to affected systems to trusted administrative users and networks until updates are installed.

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.
–
EPSSEstimate of the chance this CVE is exploited in the next 30 days. Refreshed daily.
–
agent run time
6m
cve.org record, t = 0The moment cve.org publishes the CVE in full.
not published yet
Δ 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: an exploit technique exists, but no deterministic check could cover this one.

source signals

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

  1. 2026-10-22 17:18Z

this entry in the feed

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

{
  "etk_id": "ETK-2026-2470",
  "cve_id": "CVE-2026-114625",
  "display_id": "CVE-2026-114625",
  "ghsa_id": null,
  "euvd_id": null,
  "status": "published",
  "anchor_state": "awaiting_cve",
  "title": "Actively exploited vulnerability in VeloCloud Orchestrator",
  "summary": "Security updates are available for an actively exploited zero-day affecting VeloCloud Orchestrator. The available evidence does not specify the vulnerability class, affected function, attacker impact, or conditions needed for exploitation.",
  "mitigation": "Apply the vendor security updates for VeloCloud Orchestrator promptly. Restrict access to affected systems to trusted administrative users and networks until updates are installed.",
  "vendor": null,
  "product": "VeloCloud Orchestrator",
  "affected": [],
  "cwes": null,
  "cvss_score": 9,
  "cvss_src": "ethiack_provisional",
  "cvss_vector": null,
  "epss_score": null,
  "epss_percentile": null,
  "epss_asof": null,
  "automation": "contextual",
  "check": false,
  "check_confidence_basis": null,
  "exploit": false,
  "pipeline_minutes": 6.334375866666667,
  "t0_at": null,
  "signals": {
    "trigger_signal": {
      "at": "2026-10-22T17:18:22+00:00",
      "days": -0.08459736245370371,
      "is_lower_bound": true,
      "measured_at": "2026-10-22T19:20:11.245658+00:00",
      "url": "https://www.bleepingcomputer.com/news/security/arista-patches-new-velocloud-orchestrator-zero-day-exploited-in-attacks/"
    }
  }
}

published 2026-10-22 17:25Z
last change 2026-10-22 18:56Z

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.

Protected by reCAPTCHA; the Google Privacy Policy and Terms of Service apply.