VeloCloud response brief
Six-card carousel text equivalent. Sources checked October 24, 2026.
1. Read-only access. Operator privileges.
An actively exploited SQL injection flaw lets a valid VeloCloud Orchestrator login cross the operator boundary.
Enterprise Read Only is sufficient.
A valid Enterprise Read Only portal session can lead through the SQL injection flaw to operator privileges.
2. A login is required. The role can be low.
Reach the web interface, hold a valid portal session, then exploit the affected Orchestrator.
Edge and Gateway are not affected by this CVE.
Reachable VCO web interface and valid portal session, then exploitation of the affected Orchestrator, leading to operator access.
3. The September fix is not this fix.
If you still run the older builds below, check the new cutoff. Verify the running version, not just the ticket.
Use the fixed build in your release train.
Older fixes 5.2.3.16 and 6.4.2.8 are below the new cutoffs 5.2.3.18 and 6.4.2.12. The 6.1 train is fixed in 6.1.3.10. Use later builds within the applicable train.
4. Check the addresses. Then check actions.
Arista published two attack source IPs. Search access records and correlate accounts, requests, and changes.
A match is a lead, not proof of compromise.
Vendor-published source IPs: 74.82.197.86 and 38.54.50.151. Review activity, changes, and outbound traffic.
5. What could that operator change?
Review the policies managed by your Orchestrator and the independent controls around them.
For operational sites, the network design sets the risk.
Ask who can reach the console, who approves policy changes, and who retains the evidence.
6. Fixed is one record. Investigated is another.
Keep the running-build check and the investigation result together, with named owners and open questions.
Preserve evidence before remediation where feasible.
Fixed: running build and exposure controls. Investigated: reviewed activity and remaining gaps.
