# CVE-2026-86109: Security Advisory 0182

> Attackers with upload or access privileges can install unauthorized software on VeloCloud Edge devices by bypassing signature validation during updates.

- **Severity:** High 7.5 (`CVSS:4.0/AV:N/AC:H/AT:N/PR:H/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Login needed:** An administrator
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 16 Sep 2026
- **Updated:** 17 Sep 2026
- **Also known as:** GHSA-gqff-2qm6-5664

## What is CVE-2026-86109?

CVE-2026-86109 is a high-severity vulnerability in Arista Networks VeloCloud Edge, published on 16 Sep 2026. An attacker needs administrator access to exploit it, with no action from the victim.

### Official description

The VeloCloud Edge software update workflow may accept update bundles without properly validating their signatures because the workflow does not restrict the digest algorithm used for artifact verification. An attacker with either sufficient privileges to upload packages to VeloCloud Orchestrator or credentials permitting direct access to an Edge may be able to install unauthorized software.

Weakness: CWE-347 (Improper Verification of Cryptographic Signature)

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


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

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

## Is CVE-2026-86109 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-86109 is a high-severity vulnerability in Arista Networks VeloCloud Edge, published on 16 Sep 2026. An attacker needs administrator access to exploit it, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-86109 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-86109/ (Markdown: https://insights.sbomify.com/CVE-2026-86109/index.md)
```

## Sources

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

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