# CVE-2026-17192: VeloCloud Orchestrator Missing Input Validation SSRF

> Authenticated admins can exploit missing input validation to access internal services via Server-Side Request Forgery in VeloCloud Orchestrator.

- **Severity:** Medium 6.3 (`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`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 27 Jul 2026
- **Updated:** 27 Jul 2026
- **Also known as:** GHSA-j52c-cvfp-wrxg

## What is CVE-2026-17192?

CVE-2026-17192 is a medium-severity server-side request forgery vulnerability in Arista Networks VeloCloud Orchestrator On-Prem, published on 27 Jul 2026. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

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.

Weakness: CWE-918 (Server-Side Request Forgery)

## Which versions are affected by CVE-2026-17192?


## How do I fix CVE-2026-17192?

No fix has been published for CVE-2026-17192 yet. Limit exposure of the affected software until one is available.

## Is CVE-2026-17192 being exploited?

There is no known exploitation of CVE-2026-17192 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-17192 and fix it if it is affected.

What it is: CVE-2026-17192 is a medium-severity server-side request forgery vulnerability in Arista Networks VeloCloud Orchestrator On-Prem, published on 27 Jul 2026. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-17192 in the wild and no public exploit code.

Affected product: Arista Networks VeloCloud Orchestrator On-Prem. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-17192/ (Markdown: https://insights.sbomify.com/CVE-2026-17192/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-17192
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-17192
- OSV: https://osv.dev/vulnerability/CVE-2026-17192

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-17192/
Summaries are generated and may contain mistakes; the official description above is the record.