# CVE-2026-101153: Security Advisory 0188

> Authenticated high-privilege users can exploit a path traversal flaw in Arista CloudVision to extract unintended data from the Sensor.

- **Severity:** High 7.2 (`CVSS:4.0/AV:N/AC:H/AT:N/PR:H/UI:N/VC:H/VI:N/VA:N/SC:H/SI:H/SA:H`)
- **Exploited in the wild:** Not known
- **Login needed:** An administrator
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 6 Oct 2026
- **Updated:** 6 Oct 2026
- **Also known as:** GHSA-g9x5-xpgj-754v

## What is CVE-2026-101153?

CVE-2026-101153 is a high-severity path traversal vulnerability in Arista Networks CloudVision Portal, published on 6 Oct 2026. An attacker needs administrator access to exploit it, with no action from the victim.

### Official description

On affected versions of CloudVision Portal (on-premises) or CloudVision Sensor, a path traversal vulnerability exists. An authenticated user with sufficient high privileges could exploit this to extract unintended data from the Sensor.

Weakness: CWE-22 (Improper Limitation of a Pathname to a Restricted Directory)

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


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

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

## Is CVE-2026-101153 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-101153 is a high-severity path traversal vulnerability in Arista Networks CloudVision Portal, published on 6 Oct 2026. An attacker needs administrator access to exploit it, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-101153 in the wild and no public exploit code.

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

## Sources

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

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