CVE-2026-120983: Arista Networks EOS · Improper Access Control
Affects Arista Networks EOSSource CVE Database V5
Not known to be exploited · CVSS 7.6 High : upgrade to 4.33.0F soon.
Data as of 10 Nov 2026, 20:32 UTC
Thin evidence
One scorer or none| CNA (Arista) | CVSS 3.1 | 7.6 |
|---|---|---|
| CNA (Arista) | CVSS 4.0 | 6.1 |
- Patch
- Available – fixed in 4.33.0F
CVSS:3.1/AV:A/AC:L/PR:N/UI:N/S:U/C:H/I:L/A:LExploitation 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 Arista Networks EOS to 4.33.0F.
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| Arista NetworksEOS | Affected
| Fixed in
|
AI-suggested
A fix is available in Arista EOS version 4.33.0F and later. Users should upgrade affected EOS platforms to version 4.33.0F or newer to remediate this vulnerability. There are no indications that temporary workarounds or mitigations are provided or required beyond applying the official fix.
Description
CVE-2026-120983 is an improper access control vulnerability in Arista Networks EOS affecting configurations where 802.1x is set to multi-host authenticated mode alongside Policy Based Routing (PBR). This flaw allows traffic from unauthenticated hosts to be forwarded according to PBR policies, potentially granting unauthorized network access. Additionally, Layer 2 and Layer 3 control packets from unauthenticated hosts may be copied to the device CPU. The vulnerability is rated high severity with a CVSS score of 7.6 and affects multiple EOS versions prior to 4.33.0F, which contains the fix.