Skip to content
major vulnerability· requires attention

Unauthenticated remote access to Arista CV-CUE backend can expose sensitive info or disrupt network services; impacts core networking infrastructure used enterprise-wide.

Networks

CVE-2026-102159

9.3
Critical
EPSS n/aPatch availableOct 8, 2026

Unauthenticated access to Arista CV-CUE backend exposing internal functions

common questions

Is CVE-2026-102159 being exploited?

Not confirmed. CVE-2026-102159 does not appear in CISA's Known Exploited Vulnerabilities catalog, which records only exploitation that has been observed and reported publicly. That is evidence of absence of a report, not evidence the flaw is unattacked.

How severe is CVE-2026-102159?

CVE-2026-102159 is rated Critical with a CVSS score of 9.3. Severity describes how bad exploitation would be, not how likely it is: pair it with exploitation evidence before deciding what to patch first.

Is there a patch for CVE-2026-102159?

Yes. A fix has been recorded for CVE-2026-102159. The vendor advisory is the authority on the exact fixed version — apply it from there rather than from a summary.

What does CVE-2026-102159 affect?

CVE-2026-102159 affects Arista CV-CUE backend, Arista CloudVision/CV-CUE deployments. Confirm the exact affected versions against the vendor advisory before deciding you are exposed.

What should I do about CVE-2026-102159?

Restrict CV-CUE network access (ACLs/segmentation), follow vendor mitigations, patch when vendor update is released

Exploitation status reflects CISA's KEV catalog as we last synced it. Check the catalog directly.

executive summary
technical analysis
affected
Arista CV-CUE backendArista CloudVision/CV-CUE deployments
impact

Unauthenticated network attacker can reach internal-only APIs, expose sensitive location data, and disrupt CV-CUE/management services.

action required

Immediate action required

affected versions
Arista Networks CloudVision CUE
  • affected>= 2022.3.0 and <= 2026.2.0

As published in the CVE Program record. A version outside these ranges is not a statement that it is unaffected — vendors sometimes understate a range, and distribution-backported builds carry upstream numbers that do not reflect what was patched into them.

how to fix
Remediation steps are tailored for users whose stack is affected. Add this technology to your stack to see the fix checklist.
references
get alerted

Track only the vulnerabilities that affect your infrastructure.

start for free