# CVE-2026-102161: Security Advisory 0190

> Unauthenticated attackers on adjacent networks can forge IP headers to gain administrative access to the CloudVision CUE backend.

- **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:** 6 Oct 2026
- **Updated:** 6 Oct 2026
- **Also known as:** GHSA-m4hm-2935-8pgp

## What is CVE-2026-102161?

CVE-2026-102161 is a high-severity authentication bypass vulnerability in Arista Networks CloudVision CUE, published on 6 Oct 2026. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

An unauthenticated attacker located on an adjacent private network (or any attacker routed through a reverse proxy/load balancer that forwards client headers) can forge their source IP address and gain administrative session privileges on the CV-CUE backend.

Weakness: CWE-798 (Use of Hard-coded Credentials), CWE-290 (Authentication Bypass by Spoofing)

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


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

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

## Is CVE-2026-102161 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-102161 is a high-severity authentication bypass vulnerability in Arista Networks CloudVision CUE, published on 6 Oct 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-102161 in the wild and no public exploit code.

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

## Sources

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

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