CVE-2026-114625 Hits Arista VeloCloud Orchestrator

Arista's on-premises VeloCloud Orchestrator carries a SQL injection flaw, CVE-2026-114625, and CISA added it to the Known Exploited Vulnerabilities catalog on 23 October 2026, in catalog version 2026.10.23. The required mitigation date is 26 October 2026 — three days later. If you run a VCO appliance or VM in your own environment, treat that deadline as yours even if you are not a federal agency. If your SD-WAN orchestration is vendor-hosted, CISA's description of the affected product as "on-prem" does not cover you.

What CVE-2026-114625 actually describes

CISA's entry describes a SQL injection vulnerability in the on-premises Arista VeloCloud Orchestrator that may allow a remote attacker to access privileged internal functionality and impact the VCO host.

In CISA's wording, successful exploitation "may compromise the confidentiality, integrity, and availability of the orchestrator and data managed by the orchestrator." That is the substance of the catalog entry. The VCO is the management plane for an SD-WAN estate, so a defect there is not a single-router problem — it sits above the devices it configures, and it holds the policy that flows down to them.

Two things CISA does not say, and you should not assume either way: the entry lists known ransomware campaign use as Unknown, and it names no victims and describes no exploitation detail beyond the KEV listing itself.

Am I affected? It depends on who runs the orchestrator

The affected product is the on-premises VeloCloud Orchestrator, so the first question is not "do we use VeloCloud" but "do we operate the VCO ourselves".

Ask your network team three things: is the orchestrator a VM or appliance in our own environment or a colo cage, who holds the login and the patch responsibility, and can it be reached from the public internet. That third question matters most, because CISA puts the exposure judgement on you — "stakeholders are responsible for evaluating each asset's internet exposure and ensuring adherence to BOD 26-04 patching guidelines". If you inherited an SD-WAN rollout and are not certain where the orchestrator lives, the inventory questions in our note on infrastructure and server work are the ones worth answering first.

The next 24 hours: patch, verify, then watch

Apply Arista's mitigation for CVE-2026-114625 to every on-prem VCO instance, confirm the build actually serving traffic, then watch the logs for the next several days.

CISA's required action is to "apply mitigations in accordance with vendor instructions" — the catalog entry does not itself prescribe a patch. So the work is:

• Pull the vendor instruction from Arista's support channel and follow it exactly, including any interim mitigation if a fixed build is not yet available.
• List every VCO you are responsible for — production, DR, lab, and any instance a partner or MSP runs on your behalf.
• Verify the build on the node answering traffic, not the build named in the change ticket. If the VCO sits behind a load balancer, check every node behind it.
• Close management-plane access to known addresses or VPN only. A VCO reachable from the open internet is exactly the exposure CISA is telling you to evaluate.
• Record the change against the 26 October 2026 due date so the audit trail exists.

Log the running version and the date for each asset. If you are working to BOD 26-04, that record is your evidence.

After the patch, look for what happened before it

Patching closes the door; it does not remove anyone who came through it earlier, and this vulnerability's description explicitly covers access to privileged internal functionality.

CISA's required action points at its "Forensics Triage Requirements" alongside BOD 26-04, which is a strong hint that a pre-patch window should be treated as a possible compromise window. Review the orchestrator's authentication logs for logins you cannot attribute, session activity from source addresses that do not belong to your admins, configuration changes nobody scheduled, and outbound connections from the VCO host that do not match its normal peers. If any of that turns up, go to incident response first and finish the patch second — a clean patch applied over an active intrusion mostly just makes the intrusion quieter.

What AI changes about fixing a bug of this class

Nothing in the CISA entry says how CVE-2026-114625 was found, but AI-assisted review has changed the practical economics of catching and triaging SQL injection.

SQL injection is a pattern-shaped defect, which is the kind of thing static analysis and AI code review do well: query strings assembled by concatenation, ORMs used as escape hatches, admin endpoints that build SQL straight from request parameters. What they are weaker at is the judgement call that decides whether a finding becomes a CVE — is this path reachable by an unauthenticated remote attacker, and does it land on privileged functionality. That still needs a person reading the route, the auth middleware and the database grants. A model's opinion that a code path is exploitable is not a substitute for checking the running node.

Where the tooling genuinely earns its keep is the response side: reading a vendor advisory, mapping it against an asset list, drafting the verification checklist, summarising a week of authentication logs. If you are building that kind of review into your own delivery, the AI-assisted engineering work we do is mostly about that split — automate the reading and the mapping, keep the reachability call human.

Where to start

Tonight: find out whether you run the VCO, read the running build off the node itself, and apply Arista's mitigation well before the 26 October 2026 date. If the orchestrator is internet-facing, change that today rather than at the weekend. If you would rather have someone walk the inventory and the exposure question with your team, Maysan Labs does this on cloud and infrastructure engagements — but the version check is a fifteen-minute job you can start without anyone's help.