# CVE-2024-11186: Missing authorization in CloudVision Portal

> Authenticated users can bypass access controls to perform unauthorized actions on managed EOS devices in on-premise CloudVision Portal deployments.

- **Severity:** Critical 10.0 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 8 May 2025
- **Updated:** 8 May 2025
- **Also known as:** GHSA-mf9v-44vc-62r3

## What is CVE-2024-11186?

CVE-2024-11186 is a critical missing authorization vulnerability in Arista Networks CloudVision Portal, published on 8 May 2025. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

On affected versions of the CloudVision Portal, improper access controls could enable a malicious authenticated user to take broader actions on managed EOS devices than intended. This advisory impacts the Arista CloudVision Portal products when run on-premise. It does not impact CloudVision as-a-Service.

Weakness: CWE-287 (Improper Authentication)

## Which versions are affected by CVE-2024-11186?


## How do I fix CVE-2024-11186?

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

## Is CVE-2024-11186 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2024-11186 and fix it if it is affected.

What it is: CVE-2024-11186 is a critical missing authorization vulnerability in Arista Networks CloudVision Portal, published on 8 May 2025. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2024-11186 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-2024-11186/ (Markdown: https://insights.sbomify.com/CVE-2024-11186/index.md)
```

## Sources

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

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