# CVE-2026-86106: Security Advisory 0179

> Unauthenticated attackers on the HA interconnect can trigger sensitive functions, leading to elevated command execution on Arista VeloCloud Edge units.

- **Severity:** High 8.7 (`CVSS:4.0/AV:A/AC:L/AT:N/PR:N/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 16 Sep 2026
- **Updated:** 16 Sep 2026
- **Also known as:** GHSA-9p4p-29rr-fgwc

## What is CVE-2026-86106?

CVE-2026-86106 is a high-severity missing authorization vulnerability in Arista Networks VeloCloud Edge, published on 16 Sep 2026. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

An unauthenticated actor with network access to the private HA interconnect may trigger sensitive HA peer functions without verification. This could result in elevated command execution on Edge units where HA is enabled.

Weakness: CWE-306 (Missing Authentication for Critical Functionality)

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


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

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

## Is CVE-2026-86106 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-86106 is a high-severity missing authorization vulnerability in Arista Networks VeloCloud Edge, published on 16 Sep 2026. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-86106 in the wild and no public exploit code.

Affected product: Arista Networks VeloCloud Edge. 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-86106/ (Markdown: https://insights.sbomify.com/CVE-2026-86106/index.md)
```

## Sources

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

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