Skip to content
Infrastructure

CVE-2025-5088

HIGH
High
EPSS 0.32%Patch availableJun 6, 2026

Authenticated Redis session may grant full root access to CVX cluster servers.

common questions

Is CVE-2025-5088 being exploited?

Not confirmed. CVE-2025-5088 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. EPSS currently estimates a 0.32% probability of exploitation in the next 30 days.

How severe is CVE-2025-5088?

CVE-2025-5088 is rated High. 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-2025-5088?

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

What does CVE-2025-5088 affect?

CVE-2025-5088 affects CVX cluster Redis services. Confirm the exact affected versions against the vendor advisory before deciding you are exposed.

What should I do about CVE-2025-5088?

Limit Redis exposure; rotate credentials; enable TLS; monitor for abuse.

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

executive summary
technical analysis
affected
CVX cluster Redis services
impact

Root access on all CVX cluster servers via authenticated Redis session; plaintext traffic; TLS not supported.

action required

Immediate action required

affected versions
Arista Networks EOS / CloudVision eXchange (CVX)
  • affected>= 4.34.0F and <= 4.34.1F
  • affected>= 4.33.0M and <= 4.33.4M
  • affected>= 4.32.0M and <= 4.32.6M
  • affected>= 4.31.0M and <= 4.31.8M
  • affected>= 4.30.0 and < 4.31.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