Attack ChainAIDerived
Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain
-
AccessAuthenticate as high-privilege CVP user
-
DeliveryEdit OIDC SSO provider configuration
-
ExploitSupply unvalidated arbitrary destination
-
ExecutionServer issues forged request (SSRF)
-
ImpactReach internal/arbitrary endpoint
Vulnerability Assessment
| Weakness |
CWE
OWASP Top 10:2025
A01:2025 - Broken Access Control
ASVS 5.0
V4 - API and Web Service URL allowlisting, SSRF prevention
MITRE ATT&CK
2 techniques across 2 tactics: Initial Access, Credential Access The technique list with ATT&CK links and the kill-chain view is part of the Basic plan and up. |
| Exploitation Conditions | Exploitation requires an account with specific HIGH privileges on Arista CloudVision Portal - specifically the ability to view and modify the OIDC SSO provider configuration - because the flaw is insufficient validation of that provider configuration (PR:H). The attacker must have network access to the CVP management interface (AV:N) but needs no user interaction (UI:N) and faces low attack complexity (AC:L). The dominant limiting factor is the high-privilege prerequisite: a low-privileged or unauthenticated attacker cannot reach the vulnerable configuration path, so realistic risk is confined to abuse by, or takeover of, already-privileged administrative accounts. Affected deployments are CloudVision Portal versions in the 2020.3.0-2025.3.3, 2026.1.0-2026.1.2, and 2026.2.0 ranges per EUVD; patched releases from Arista remove exposure. |
| Impact | This is a genuinely low-to-moderate priority issue despite the SSRF classification (CWE-918), and the available signals are notably consistent rather than conflicting. The CVSS 4.0 vector (AV:N/AC:L/AT:N/PR:H/UI:N) describes a network-reachable, low-complexity attack but one that explicitly requires HIGH privileges (PR:H) - matching the description's 'user with specific high privileges' who can alter OIDC SSO provider configuration. Impact is constrained: the vulnerable system itself sees no confidentiality/integrity/availability impact (VC:N/VI:N/VA:N), with only a LOW subsequent-system confidentiality impact (SC:L), reflecting classic SSRF where the harm is request redirection to other reachable destinations rather than direct compromise of CloudVision itself. CISA's SSVC framework reinforces low urgency: Exploitation=none (no observed exploitation), Automatable=no, Technical Impact=partial. There is no KEV listing and no public exploit identified at time of analysis, so there is no evidence of active or opportunistic exploitation. The base score of 5.1 (Medium) is driven down by the PR:H requirement - an attacker already holding high administrative privileges is the precondition, which greatly limits real-world risk. No key signals contradict each other here; the main residual uncertainty is the exact security boundary being crossed (an already-privileged admin abusing SSO config), which should be confirmed against the Arista advisory. |
| Exploit ScenarioDerived | An authenticated user already holding high administrative privileges on Arista CloudVision Portal modifies the OIDC SSO provider configuration to point authentication/discovery requests at an attacker-controlled or internal destination. Because validation of the provider configuration is insufficient, the server can be coerced into issuing requests to arbitrary destinations, potentially reaching internal services not otherwise exposed. No public exploit code has been identified, and exploitation requires pre-existing high privileges plus network access to the management interface. |
Get an e-mail when this CVE is exploited, patched or re-scored. Free account.
Alert meAnalysisAIv1 – Oct 06, 2026
Server-side request forgery (SSRF) in Arista CloudVision Portal arises from insufficient validation of OIDC SSO provider configuration, allowing a user holding the specific high-privilege right to view and modify that configuration to direct CVP-originated requests to arbitrary destinations. The practical impact is limited rather than systemic: the CVSS 4.0 base of 5.1 and our independent CVSS 3.1 assessment (AV:N/AC:L/PR:H/UI:N/S:C/C:L/I:N/A:N) both reflect that the attacker must already be a highly privileged CVP administrator with network reach to the management interface, and that the consequence is a low-confidentiality information-disclosure primitive rather than code execution or service disruption. There is no public exploit identified at time of analysis and no confirmed active exploitation (SSVC: Exploitation=none, Automatable=no); a vendor patch is available via Arista security advisory 0186, and the main residual risk is abuse or takeover of an already-privileged administrative account.
RemediationAI
Vendor patches are available: Arista has published Security Advisory 0186 covering this issue, and administrators should upgrade CloudVision Portal to the fixed release designated for their maintenance train (the advisory lists the corrected versions for the 2025.3.x, 2026.1.x, and 2026.2.x lines and provides the migration path for older 2020.3.0+ deployments that must move to a supported train). Because no exact fix version is reproduced in the upstream intelligence feed, confirm the target build against advisory 0186 before scheduling the upgrade rather than assuming a version number. Until patched, the most effective compensating controls follow directly from the high-privilege prerequisite: tighten RBAC so that view/modify rights on the OIDC SSO provider configuration are granted only to the smallest possible set of trusted administrators, and audit those accounts for compromise - this removes the ability to reach the vulnerable path at all. Additionally, restrict outbound egress from CVP nodes to an allowlist containing only the legitimate identity-provider hosts, which blunts any SSRF attempt by blocking access to internal services and cloud metadata endpoints; the trade-off is that adding or changing federated identity providers then requires an egress-policy update, and overly broad allowlists (for example, permitting whole internal RFC1918 ranges) restore most of the exposure. If the SSO configuration is not in active use, disabling or removing unused OIDC providers eliminates the attack surface entirely, with the side effect of forcing local or alternative authentication. Finally, monitor CVP logs and identity-provider callbacks for unexpected issuer/discovery URL modifications and for outbound requests originating from the CVP management plane.
Affected VersionsENISA
Affected Packages
Source: OSV (Open Source Vulnerabilities)
Affects your stack
Affects 1 package in euvd
Checking this CVE against your own stacks and servers is part of the Basic plan and up.
Technical ContextAI · show details
The flaw is an instance of CWE-918 (Server-Side Request Forgery) in the OpenID Connect SSO integration of Arista CloudVision Portal. OIDC provider configuration typically consists of operator-supplied URLs - the issuer identifier, the discovery document (/.well-known/openid-configuration), the JWKS key-set URI, and authorization/token endpoints - which the CVP backend fetches server-side during login federation, key rotation, or configuration validation. Because those values are not sufficiently validated (for example, not restricted to an allowlist of trusted identity-provider hosts, and not guarded against loopback, link-local, or RFC1918 targets), a privileged operator can point a configured provider at an arbitrary destination and cause CVP itself to issue the request from its network position. The CVSS 4.0 vector (AV:N/AC:L/AT:N/PR:H/UI:N, with subsequent-system confidentiality SC:L) and our CVSS 3.1 assessment (S:C/C:L/I:N/A:N) agree that this yields a low-severity read-only exposure - useful for reaching internal-only HTTP services, cloud metadata endpoints, or management APIs inside the CVP enclave - but not integrity or availability loss. Note that the privilege bar (PR:H) is the dominant constraint: the vulnerable configuration path is unreachable to unauthenticated or low-privileged users, so the threat model is a malicious or compromised CVP administrator rather than an external attacker.
Know when the next one hits your stack
- Watch products and get an email when something new is published
- Check this CVE against your own stack and servers
- Exploit and PoC references, threat intelligence from 22 sources
No credit card · 7-day full trial
Severity by source
CVSS:4.0/AV:N/AC:L/AT:N/PR:H/UI:N/VC:N/VI:N/VA:N/SC:L/SI:N/SA:N
Requires high-privilege access to OIDC SSO configuration (PR:H); network-reachable with low complexity; SSRF redirects requests to other systems (S:C) yielding only limited confidentiality exposure (C:L), no integrity/availability impact.
Primary rating from Vendor (arista).
CVSS VectorVendor: arista
Lifecycle Timeline
1DescriptionCVE.org
Insufficient validation of OIDC SSO provider configuration could allow a user with specific high privileges to direct requests to arbitrary destinations.
Threat Intelligence Overview
How this decision was reached
The engine reads each signal below and applies a fixed list of rules from top to bottom. The first rule that matches sets the recommended action – like a statement, every line is shown.
What every action level means
SSVC AssessmentENISA
Priority Score
Attack Technique
Server-Side Request Forgery exploits applications that fetch remote resources based on user-supplied URLs.
EUVD-2026-93945
GHSA-x5hx-36j4-jgqp
NVD
CVE.org
EPSS
Vulnrichment
Exploit-DB