CVE-2025-6188: Arista Networks EOS · 288
Affects Arista Networks EOSSource CVE Database V5
Not known to be exploited · CVSS 7.5 High.
Data as of 26 Oct 2026, 10:12 UTC
- EPSS
- 0.4% chance of exploitation in 30 days – higher than 35% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:NExploitation evidence
Disclosed: evidence found.
CVE published 25 Aug 2025
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by 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 26 Oct 2026.
What to do
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| Arista Networks EOS | Affected
| Fixed in– |
AI-suggested
European organizations should implement several targeted mitigation strategies beyond generic advice: 1) Immediately audit network devices running affected versions of Arista EOS to identify vulnerable systems. 2) Restrict access to UDP port 3503 at network boundaries using firewall rules or access control lists (ACLs) to limit exposure to trusted sources only, ideally isolating management and diagnostic traffic. 3) Employ network segmentation to separate critical infrastructure from less trusted network zones, reducing the attack surface. 4) Monitor network traffic for anomalous UDP packets with source port 3503, leveraging IDS/IPS systems to detect and alert on suspicious activity related to LspPing Echo Reply messages. 5) Engage with Arista Networks for timely patch releases and apply updates as soon as they become available. 6) Review and enhance authentication mechanisms for UDP-based services where possible, including implementing cryptographic validation or additional verification layers. 7) Conduct regular security assessments and penetration testing focusing on network protocol handling to identify similar weaknesses. These steps will help reduce the likelihood of exploitation and limit potential damage if an attack occurs.
Description
On affected platforms running Arista EOS, maliciously formed UDP packets with source port 3503 may be accepted by EOS. UDP Port 3503 is associated with LspPing Echo Reply. This can result in unexpected behaviors, especially for UDP based services that do not perform some form of authentication.