Skip to main content

Arista VeloCloud Orchestrator CVE-2026-17192

| EUVDEUVD-2026-49373 MEDIUM
Server-Side Request Forgery (SSRF) (CWE-918)
2026-07-27 Arista GHSA-j52c-cvfp-wrxg
6.3
CVSS 4.0 · Vendor: Arista
View

Attack ChainAIDerived

Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain

  1. Access
    Authenticate as Enterprise Standard Admin
  2. Delivery
    Submit crafted input to VCO feature
  3. Exploit
    Server issues SSRF request to internal service
  4. Execution
    Reach service not otherwise accessible
  5. Impact
    Enumerate or interact with internal back-end

Vulnerability Assessment

Weakness
CWE
OWASP Top 10:2025
A01:2025 - Broken Access Control
ASVS 5.0
V4 - API and Web Service URL allowlisting, SSRF prevention
MITRE ATT&CK

2 techniques across 2 tactics: Initial Access, Credential Access

The technique list with ATT&CK links and the kill-chain view is part of the Basic plan and up.

Exploitation Conditions

Requires an authenticated tenant account with a minimum role of Enterprise Standard Admin on Arista VeloCloud Orchestrator On-Prem; the attacker must reach the specific vulnerable VCO feature that fails to validate caller-supplied input. Realistic impact is further gated by which internal (otherwise non-accessible) services the Orchestrator can route to in a given deployment. Affected: VCO On-Prem 6.1.0<6.1.3.4, 5.2.0<5.2.3.14, and 6.4.0<6.4.2.4; upgrading to the fixed releases removes the condition. Limiting factors: privileged role required (not unauthenticated), no user interaction of a victim needed, and impact is confined to subsequent internal systems rather than the Orchestrator's own confidentiality/integrity/availability.

Impact

This is a genuine but bounded, mid-severity issue rather than an urgent priority. The vendor CVSS 4.0 base of 6.3 (AV:N/AC:L/AT:N/PR:L/UI:N) correctly reflects an authenticated, network-reachable SSRF whose damage lands on subsequent internal systems (SC:H/SI:L) rather than on the Orchestrator itself (VC:N/VI:N/VA:N). All exploitation signals point away from imminent mass exploitation: CISA SSVC scores Exploitation=none, Automatable=no, Technical Impact=partial; there is no CISA KEV listing and no public exploit code identified. EPSS is 2.34% (82nd percentile) - modestly elevated versus the median but not indicative of active, widespread exploitation, and it is consistent with the vendor's own statement that the flaw was found internally with no known malicious use. The key limiting factor is the required privilege: exploitation demands a minimum role of Enterprise Standard Admin (PR:L), so this is an authenticated privilege/isolation-boundary bypass, not an unauthenticated internet-facing RCE. No signals are strongly conflicting; the main caveat is that the real blast radius depends on what internal services the Orchestrator can reach, which is deployment-specific.

Exploit ScenarioDerived

An attacker holding (or having compromised) an account with at least the Enterprise Standard Admin role sends a crafted request to the vulnerable VCO feature, supplying an input the feature fails to validate. The Orchestrator then issues attacker-directed requests on behalf of the tenant to internal services that are not otherwise reachable, enabling reconnaissance or interaction with back-end systems. No public proof-of-concept or exploit code has been identified at the time of analysis.

This Month Plan within 30 days. Why: MEDIUM severity (CVSS 4.0-6.9).
Patch available 2.3% exploitation probability (EPSS)

Get an e-mail when this CVE is exploited, patched or re-scored. Free account.

Alert me

AnalysisAIv1 – Sep 16, 2026

Server-side request forgery in Arista VeloCloud Orchestrator On-Prem lets an authenticated tenant account with at least the Enterprise Standard Admin role induce the Orchestrator to issue requests to internal services that are otherwise unreachable, because a VCO feature fails to sufficiently validate caller-supplied input. Impact is scoped to subsequent systems rather than the Orchestrator itself (low confidentiality/integrity, no availability effect), so real risk depends on what internal services a given deployment can route to. No public exploit code or active exploitation is known - Arista discovered the issue internally and confirms no malicious use in customer networks - although EPSS places it around the 82nd percentile, and vendor patches are available for the affected release trains.

RemediationAI

Apply the vendor-released fixed builds for each affected train: VeloCloud Orchestrator On-Prem 5.2.3.14 (or later in the 5.2 line), 6.1.3.4 (or later in the 6.1 line), and 6.4.2.4 (or later in the 6.4 line), per Arista Security Advisory 0145 at https://www.arista.com/en/support/advisories-notices/security-advisory/24365-security-advisory-0145. Until upgrades complete, reduce the attack surface by restricting Enterprise Standard Admin (and higher) tenant assignments to identities that genuinely require them and by auditing/soaking up privileged tenant accounts, since the issue is only reachable with that role; be aware this is a role-minimization trade-off that may disrupt legitimate administrative workflows. Where the deployment permits it, segment or firewall the Orchestrator management interface so it cannot reach internal services unrelated to orchestration, understanding that overly tight egress rules can break legitimate VCO-to-infrastructure communication and should be validated in a test environment first. If the vulnerable internal-request feature can be disabled or its input restricted via configuration, do so as a temporary compensating control, accepting the loss of that functionality. Monitor Arista advisories for updated guidance and watch Orchestrator logs for anomalous outbound requests originating from the VCO to unexpected internal endpoints.

Affected VersionsENISA

VeloCloud Orchestrator On-Prem 6.1.0 <6.1.3.4
VeloCloud Orchestrator On-Prem 5.2.0 <5.2.3.14
VeloCloud Orchestrator On-Prem 6.4.0 <6.4.2.4

Affected Packages

euvd velocloud_orchestrator_on_prem fix: 5.2.3.14, 6.1.3.4, 6.4.2.4

Source: OSV (Open Source Vulnerabilities)

Affects your stack

Affects 1 package in euvd

Checking this CVE against your own stacks and servers is part of the Basic plan and up.

Technical ContextAI · show details

The root cause is CWE-918 (server-side request forgery): a feature of the VeloCloud Orchestrator (VCO) On-Prem web/management plane accepts caller-supplied input - most plausibly a URL, hostname, or endpoint parameter - and forwards or fetches it without adequate validation, allowing the request to be redirected toward internal services that the caller could not reach directly. Because the vulnerable component runs inside the management/orchestration tier, it can act as a trusted pivot into network segments that are not exposed to tenant-facing interfaces. The submitted CVSS 4.0 vector (AV:N/AC:L/AT:N/PR:L/UI:N, with SC:H and SI:L alongside VC/VI/VA:N) and the independent CVSS 3.1 assessment (AV:N/AC:L/PR:L/UI:N/S:C/C:L/I:L/A:N) both describe a scope-changing, low-severity-impact SSRF that requires authenticated access with a privileged tenant role. The affected CPE is arista_networks:velocloud_orchestrator_on-prem, indicating the on-premises deployment form of the product, consistent with EUVD's affected ranges: 6.1.0 before 6.1.3.4, 5.2.0 before 5.2.3.14, and 6.4.0 before 6.4.2.4. SSVC rates exploitation as none, automatable as no, and technical impact as partial, matching the assessment that this is bounded rather than an urgent, wormable condition. Per the independent assessment, exploitation requires an authenticated tenant account holding at least the Enterprise Standard Admin role and reachability to the specific vulnerable feature; no victim user interaction is needed, and impact falls on downstream internal systems rather than the Orchestrator's own confidentiality, integrity, or availability.

Know when Velocloud Orchestrator On Prem gets its next vulnerability

  • Watch products and get an email when something new is published
  • Check this CVE against your own stack and servers
  • Exploit and PoC references, threat intelligence from 22 sources

No credit card · 7-day full trial

Severity by source

Vendor (Arista) PRIMARY 6.3 HIGH
CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:N/VI:N/VA:N/SC:H/SI:L/SA:N/S:P
vuln.today AI 6.4 MEDIUM

Authenticated Enterprise Standard Admin (PR:L) SSRF crosses a trust boundary to internal services (S:C) with limited confidentiality/integrity impact on those systems and no direct impact on the Orchestrator.

3.1 AV:N/AC:L/PR:L/UI:N/S:C/C:L/I:L/A:N
4.0 AV:N/AC:L/AT:N/PR:L/UI:N/VC:N/VI:N/VA:N/SC:H/SI:L/SA:N

Primary rating from Vendor (Arista).

CVSS VectorVendor: Arista

Attack Vector
Network
Attack Complexity
Low
Attack Requirements
None
Privileges Required
Low
User Interaction
None
Vulnerable system: Confidentiality
None
Vulnerable system: Integrity
None
Vulnerable system: Availability
None
Subsequent system: Confidentiality
High
Subsequent system: Integrity
Low
Subsequent system: Availability
None

Lifecycle Timeline

3
Patch available
Jul 27, 2026 - 18:02 EUVD
Severity Changed
Jul 27, 2026 - 17:22 NVD
HIGH MEDIUM
CVSS changed
Jul 27, 2026 - 17:22 NVD
8.5 (HIGH) 6.3 (MEDIUM)

DescriptionCVE.org

A VCO feature does not sufficiently validate caller-supplied input, allowing requests to be made on behalf of authenticated tenant accounts to internal services that are not otherwise accessible. This vulnerability requires a minimum role of Enterprise Standard Admin.

This issue was discovered internally by Arista and the company is not aware of any malicious uses of this issue in customer networks.

Threat Intelligence Overview

EPSS Score
2.3%
Top 18% exploitable
Prevalence
Medium
Enterprise SD-WAN orchestrator, common in networks but a specific vendor product
Data Quality
5 sources
Confidence: Medium

How this decision was reached

The engine reads each signal below and applies a fixed list of rules from top to bottom. The first rule that matches sets the recommended action – like a statement, every line is shown.

SignalValue
Severity MEDIUM
CISA KEV No
Public POC No
EPSS 2.3%
Patch available Yes
Active threat No
Deciding rule
MEDIUM severity (CVSS 4.0-6.9)
What every action level means
Emergency Immediate action required. Criteria: CRITICAL + in CISA KEV (actively exploited) without patch, OR CRITICAL + EPSS > 30% without patch, OR CRITICAL + active threat signals without patch.
Act Now Prioritize within 24-48h. Criteria: in KEV with patch available, OR CRITICAL + public POC, OR HIGH + EPSS > 10%, OR CRITICAL + active threat, OR any CRITICAL severity.
This Week Schedule remediation this week. Criteria: HIGH severity (CVSS 7.0-8.9). Patch within normal change window.
This Month Plan within 30 days. Criteria: MEDIUM severity (CVSS 4.0-6.9), lower exploitation probability. Include in regular patch cycle.
Monitor Track and reassess. Criteria: LOW severity (CVSS 0.1-3.9), minimal exploitation risk. No immediate action needed.

SSVC AssessmentENISA

SSVC Decision· derived
Scheduled
Exploitation
None
System Exposure· derived
Open
Automatable
No
Human Impact· derived
Medium
Technical Impact
Partial

Priority Score

34
Low Medium High Critical
KEV: 0
EPSS: +2
CVSS: +32
PoC: 0
Weaponized: 0
Threat intel: 0
Gov advisory: 0

Attack Technique

Server-Side Request Forgery exploits applications that fetch remote resources based on user-supplied URLs.

This site uses cookies essential for authentication and security. No tracking or analytics cookies are used. Privacy Policy