Severity by source
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/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:P/AU:X/R:X/V:X/RE:X/U:X
Primary rating from Vendor (Arista) · only source for this CVE.
CVSS VectorVendor: Arista
Lifecycle Timeline
4DescriptionCVE.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.
AnalysisAI
We need to produce a JSON object with all the specified fields. The input provides CVE-2026-17192, description, CVSS 4.0 vector, CWE, tags, references, CPE, and note about internal discovery. No EPSS, no KEV, no POC mentioned. So exploitation status: no public exploit identified. Patch status: need to check references. The advisory URL is provided. We need to extract patch version info. Since it's a security advisory from Arista, likely they have a fixed version. But the input does not explicitly state the fix version. We should check the advisory URL content? But we only have the URL, not the content. However, the instruction says "Use ALL the data provided". The references contain advisory URL. We can assume that patch is available per vendor advisory, but we don't have an exact version. The CPE indicates the product is "arista_networks:velocloud_orchestrator_on-prem". So product name: "Velocloud Orchestrator On-Prem". But careful: The description says "A VCO feature" - VCO likely stands for Velocloud Orchestrator. So product_name: "Velocloud Orchestrator". The CPE says "velocloud_orchestrator_on-prem". So we'll use "Velocloud Orchestrator".
Summary: Need original synthesis, not copying description. The vulnerability is an SSRF via VCO feature that doesn't validate input, allowing authenticated tenant admins to make requests to internal services. Minimum role Enterprise Standard Admin. No known exploitation.
Technical context: CWE-918 is Server-Side Request Forgery. Explain SSRF, how the VCO feature works, using CPE to identify affected product.
Risk assessment: CVSS 4.0 vector: AV:N/AC:L/AT:N/PR:L/UI:N/VC:N/VI:N/VA:N/SC:H/SI:L/SA:N. So low impact on vulnerable system (no CIA), but high impact on subsequent system (confidentiality high, integrity low). That means the SSRF allows accessing internal services (subsequent system) and potentially reading sensitive data. But note that exploit requires authenticated user with Enterprise Standard Admin role. So PR:L is
Same weakness CWE-918 – Server-Side Request Forgery (SSRF)
View allShare
External POC / Exploit Code
Leaving vuln.today
EUVD-2026-49373
GHSA-j52c-cvfp-wrxg