Skip to content
Networks

CVE-2026-2379

8.2
High
EPSS 0.23%Patch availableJun 6, 2026

IPsec VPN tunnels unstable on Arista EOS after interface flaps/restarts.

common questions

Is CVE-2026-2379 being exploited?

Not confirmed. CVE-2026-2379 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.23% probability of exploitation in the next 30 days.

How severe is CVE-2026-2379?

CVE-2026-2379 is rated High with a CVSS score of 8.2. 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-2379?

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

What does CVE-2026-2379 affect?

CVE-2026-2379 affects Arista EOS with hardware IPSec support (IPsec features enabled). Confirm the exact affected versions against the vendor advisory before deciding you are exposed.

What should I do about CVE-2026-2379?

Apply EOS firmware update when released; monitor VPN status

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

executive summary
technical analysis
affected
Arista EOS with hardware IPSec support (IPsec features enabled)
impact

VPN tunnels may re-establish with SA sequence-number mismatches, causing disruption of secure communications.

action required

Patch when possible

affected versions
Arista Networks EOS
  • affected>= 4.34.0 and <= 4.34.3M
  • affected>= 4.33.0M and <= 4.33.5M
  • affected>= 4.32.0M and <= 4.32.7M
  • affected>= 4.31.0M and <= 4.31.9M
  • affected>= 4.30.0F and < 4.31.0
  • affected>= 4.29.0F and < 4.30.0
  • affected>= 4.28.0F and < 4.29.0
  • affected>= 4.27.1F and < 4.28.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