# CVE-2026-101152: Security Advisory 0187

> Remote attackers can exploit insufficient SSO validation to redirect users to malicious sites, potentially stealing authentication credentials.

- **Severity:** High 7.6 (`CVSS:4.0/AV:N/AC:H/AT:P/PR:N/UI:P/VC:H/VI:H/VA:N/SC:N/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** A user has to click or open something
- **Fix available:** No
- **Published:** 6 Oct 2026
- **Updated:** 6 Oct 2026
- **Also known as:** GHSA-8xp4-5fqf-wj9g

## What is CVE-2026-101152?

CVE-2026-101152 is a high-severity vulnerability in Arista Networks CloudVision Portal, published on 6 Oct 2026. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.

### Official description

Insufficient validation in the Single Sign-On (SSO) login flow could allow a remote, unauthenticated attacker to craft a URL that, when clicked by a user, causes the identity provider (IdP) to deliver authentication material to an attacker-controlled URL instead of to CloudVision.

Weakness: CWE-601 (URL Redirection to Untrusted Site)

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


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

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

## Is CVE-2026-101152 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-101152 is a high-severity vulnerability in Arista Networks CloudVision Portal, published on 6 Oct 2026. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2026-101152 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-101152/ (Markdown: https://insights.sbomify.com/CVE-2026-101152/index.md)
```

## Sources

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

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