PolicyCortex
Request Access
Summary
  • Arista confirms active exploitation in the wild. The flaw affects on-premises VeloCloud Orchestrator deployments.
  • Any authenticated user can gain operator privileges. That user can pose as a local superuser operator.
  • Arista patched its hosted service. Patched levels include 5.2.3.18, 6.1.3.10, and 6.4.2.12.
  • Arista published two attack addresses: 74.82.197.86 and 38.54.50.151. Check your logs for both today.

A basic account becomes the top account

A software-defined wide area network (SD-WAN) links branch sites over shared connections. VeloCloud Orchestrator (VCO) is the web console that manages that network. Admins use it to configure and monitor edge devices.

Arista confirms attackers are exploiting a flaw in on-premises VCO. The flaw is tracked in the Common Vulnerabilities and Exposures program as CVE-2026-114625. Arista published the issue as Security Advisory 0199 on October 22, 2026, scoring it 9.9 out of 10 under CVSS version 3.1. Read the full Arista Security Advisory 0199.

How the escalation works

The attack starts with a valid signed-in session. The user needs basic privileges and access to the web interface. Arista describes a Structured Query Language (SQL) injection path. The attack needs no further user interaction.

On an affected system, any authenticated user can gain operator privileges. That user can pose as a local superuser operator. The prize is functions meant for internal use only. Those functions were never meant to be reachable remotely.

Arista warns about the wider impact too. Successful exploitation may harm confidentiality, integrity, and availability. The risk covers the orchestrator and the data it manages.

Hosted is patched. On-premises is yours.

Arista says it already patched its hosted VCO service. The patched levels are 5.2.3.18, 6.1.3.10, and 6.4.2.12. Those numbers describe the hosted service state.

On-premises customers run their own orchestrators. Nobody patches those systems for them. Each customer must patch or check for compromise.

PolicyCortex does not patch Arista gear. Your Arista support path owns that work.

What to check now

Arista published indicators of compromise (IOCs) for this flaw. The two Internet Protocol (IP) addresses are 74.82.197.86 and 38.54.50.151. Block both addresses and search your logs for them.

Arista also lists log signs worth hunting. Look for requests with unusual path components. Look for encoded characters and references to internal services. Look for high request rates and odd administrator activity.

Restrict the web interface to administrative networks for now. Preserve logs before remediation where you can. Arista lists web, backend, system, and database logs. It also lists file system timestamps. Contact the Arista Technical Assistance Center (TAC) if you suspect compromise.

The governance lesson

Management planes are part of the system. They are not side tools outside the boundary. A console that configures every edge device carries full network risk.

Governance means you fully understand that layer. Inventory every orchestrator you run. Record its version, its owner, and its patch state. Record who can sign in and from where.

An inventory that skips management planes has a hole. This flaw walked through exactly that hole.

Sources

Next step

Want management plane patch evidence collected on a schedule? See how PolicyCortex reads it from the live tenant.

Questions on this record
What is this flaw?
It is a Structured Query Language injection flaw in VeloCloud Orchestrator. An authenticated user can escalate to operator or superuser rights.
Is the hosted service patched?
Yes. Arista says it patched hosted deployments. The patched levels are 5.2.3.18, 6.1.3.10, and 6.4.2.12.
What must on-premises customers do?
Patch to a fixed level from Arista. Then check logs for the two published attack addresses.

Related records

Guides and articles describe the work. The evidence that work produces is described in three proof pages and one architecture page.

proof.state
Proof of State. What the environment was, as of a date someone else picks: point-in-time records, content hashed and chained.
proof.change
Proof of Change. Who or what altered the environment, under what authority, with before and after state hashes.
proof.agency
Proof of Agency. What a machine was permitted to do before it acted, what it did, and what would have stopped it.
architecture
Architecture. How the chain is built and where it lives: inside your tenant, with no egress of evidence.

Further reading in this register

  1. GitLab Critical Flaw: Unauthenticated Code Execution on the ServerCVE-2026-110264 scores 10.0 Critical and lets an unauthenticated user run code on a GitLab server. The fix is a patch release.5 min
  2. Four Exploited Flaws Hit the Firewall, the Mail Gateway, and the Backup ServerCISA added four exploited flaws on October 14, 2026. They hit a Palo Alto Networks firewall, a Cisco email gateway, and an Ahsay backup server.5 min
  3. PwnEscape: The Linux Kernel Flaw That Escapes the Virtual MachineCVE-2026-99999 scores 9.3 Critical and lets a guest VM read host memory, crash the host, and run code as root. The fix is a host kernel update. Guest patches do not help.5 min

Verify the record this entry describes.

Request AccessBook a call
Published
Last updated
Unchanged since publication
Author
Leonard Esere