On affected platforms running Arista EOS with Border Gateway Protocol (BGP) changing the BGP listen port from its
Source GCVE Database
Not known to be exploited · CVSS 8.2 High : upgrade to 4.33.0F or 4.32.0F soon.
Data as of 10 Nov 2026, 23:19 UTC
Thin evidence
One scorer or none| CNA (Arista) | CVSS 3.1 | 8.2 |
|---|---|---|
| CNA (Arista) | CVSS 4.0 | 8.3 |
- Patch
- Available – fixed in 4.33.0F, 4.32.0F
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:HExploitation evidence
Disclosed: evidence found.
CVE published 10 Nov 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: 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 10 Nov 2026.
What to do
Upgrade EOS to 4.33.0F or 4.32.0F.
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| Arista NetworksEOS | Affected
| Fixed in
|
AI-suggested
Users should avoid changing the BGP listen port from its default value unless they implement equivalent ACL protections manually to prevent unauthorized BGP peering. Monitor vendor advisories for any forthcoming patches or official guidance.
Description
On Arista EOS platforms running Border Gateway Protocol (BGP), changing the BGP listen port from its default disables the default protective Access Control List (ACL) rules that guard against unexpected BGP peering attempts. This configuration change can lead to unauthorized or unexpected BGP connections.