dbcve.org
Improper Input ValidationWeakness · CWE-20

CVE-2025-5089

MEDIUM · 6.5 CVSS v3.1 Published 2026-06-05
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
71/100
Remediation priority · Elevated
Remotely reachable Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
In a CVX cluster, an EOS switch connected to a CVX server is not resilient to certain malformed messages received from the connected CVX server. Similarly, the CVX server is not resilient to certain malformed messages received from the connected EOS switch. This leads to either a Sysdb agent crash on the EOS device causing a soft reset of the switch or agent crashes on the CVX server causing instability of the CVX cluster. An attacker could use this behavior to create a denial of service (DoS) scenario. Note that this would require the attacker to already have a high privilege access to the connected device to be able to send custom TCP packets. EOS switches that are not connected to a CVX server are not impacted.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · moderate confidence

In CVX clusters, the EOS switch and CVX server communication lacks proper validation of incoming messages. When either device receives malformed TCP messages from its connected peer, it triggers either a Sysdb agent crash on EOS (causing switch reset) or an agent crash on the CVX server (causing cluster instability). Exploitation requires high-privilege access to the connected device.

MitigationAwait vendor-provided patch from Arista; isolate CVX management network access to trusted personnel only. Consider network segmentation to limit exposure of CVX management interfaces.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
Low
User interaction
None
Scope
Unchanged
Confidentiality
None
Integrity
None
Availability
High

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Confirm CVX cluster is enabled
    On the CVX server, check if CVX is running in cluster mode by reviewing /etc/cvx/cvx.conf or running 'show cvx cluster status' if available. On EOS, check for CVX connections via 'show management api cvp' or 'show cvx connections'.
    Affected if CVX clustering is configured and active between EOS switches and CVX servers
  2. Verify EOS version
    Run 'show version' on the EOS switch and compare the EOS software version to any Arista security advisories for CVE-2025-5089. Look for the specific EOS version string in the output.
    Affected if The EOS version matches the vulnerable version range disclosed in the Arista security advisory for this CVE
  3. Verify CVX version
    Run 'show cvx version' on the CVX server or check the CVX package version via 'rpm -q cvx' or 'apt list --installed' depending on the OS. Compare to the affected versions in the advisory.
    Affected if The CVX version matches the vulnerable version range disclosed in the Arista security advisory for this CVE
  4. Check for CVX management network exposure
    Review the network configuration for CVX management interfaces. Check if the CVX cluster communication ports (typically TCP 443 for HTTPS) are exposed to untrusted networks by reviewing interface configurations and ACLs.
    Affected if CVX management interfaces are accessible from networks outside of trusted administrative segments
  5. Inspect Sysdb agent stability
    On EOS, run 'show sysdb hardware' or check recent crash logs via 'show logging' looking for Sysdb agent crashes. On CVX, check /var/log/cvx.log or equivalent for agent crash entries.
    Affected if Recent Sysdb agent crashes or unexpected agent restarts are logged on EOS or CVX nodes in the cluster

A system is affected if it runs a vulnerable EOS or CVX version in a CVX cluster configuration where the management interface is network-accessible.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

From vendor data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Await vendor-provided patch from Arista; isolate CVX management network access to trusted personnel only. Consider network segmentation to limit exposure of CVX management interfaces.

Have this fixed Scoped from the published advisory
  • Consultation3.0 h
  • Implementation6.0 h
  • Testing6.0 h
  • Review / QA3.0 h
18.0 hours of engineering $3,120
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $4,992.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2025-5089 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2025-5089 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data