Skip to main content
CVE-2026-120974VulnerabilityPublished

On affected platforms running Arista EOS with IPsec AutoVPN Feature configured with dynamic paths, the configured IPsec replay window may not be applied as expected

Source GCVE Database

0
Compare
Authoritative record:CVE-2026-120974· Medium 5.3

Not known to be exploited · CVSS 5.3 Medium · fixed in 4.33.0F : update EOS when convenient.

Data as of 10 Nov 2026, 22:34 UTC

CVSS 3.1 base score
5.3Medium
How severe the flaw is on the 0–10 CVSS scale.

Thin evidence

One scorer or none
CVSS scores by source
CNA (Arista)CVSS 3.15.3
CNA (Arista)CVSS 4.06.9
Patch
Available – fixed in 4.33.0F, 4.32.0F, 4.31.0F +2
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:L

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 10 Nov 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponized: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 10 Nov 2026.

What to do

Upgrade to a fixed release listed under Affected software.

Affected software

ProductAffectedFixed in
Arista NetworksEOSAffected
  • >=4.27.0F <4.28.0F
  • >=4.28.0F <=4.28.13M
  • >=4.29.0F <4.30.0F
  • >=4.30.0F <4.31.0F
  • >=4.31.0F <4.32.0F
  • >=4.32.0F <4.33.0F
  • >=4.33.0F <=4.33.8M
  • >=4.34.0F <=4.34.7M
  • >=4.35.0F <=4.35.5M
  • >=4.36.0F <=4.36.1F
Fixed in
  • 4.33.0F
  • 4.32.0F
  • 4.31.0F
  • 4.30.0F
  • 4.28.0F

Description

On affected platforms running Arista EOS with IPsec AutoVPN Feature configured with dynamic paths, the configured IPsec replay window may not be applied as expected. As a result, IPsec anti-replay protection may be silently inactive even when it has been configured via an SA policy, contrary to the operator's expectation. This issue does not allow decryption of the affected IPsec traffic, but it may allow replay of previously valid protected traffic.

References

Community reviews

Loading reviews…