CVE-2026-73776: Authenticated Signature Verification Bypass Leading to Arbitrary Code Execution in AOS-CX
Published Sep 1, 2026
·Updated
A signature verification bypass vulnerability exists in the command line interface of AOS-CX. Successful exploitation could allow an authenticated malicious actor with administrative privileges to execute arbitrary code on the underlying operating system, when certain pre-conditions outside of the attacker’s control are met.
Affected Software
161 affected components
Arista Networks AOS-CX
All of the following
Any of the following
HPE Arubaos-cx<=10.10.1180
HPE Arubaos-cx>=10.13.0000<=10.13.1180
HPE Arubaos-cx>=10.16.0000<=10.16.1051
HPE Arubaos-cx>=10.17.0000<=10.17.1021
HPE Arubaos-cx=10.18.0001
Any of the following
HPE Aruba Cx 10000-48y6c \(r8p13a\)
HPE Aruba Cx 10000-48y6c \(r8p14a\)
HPE Aruba Cx 10000-48y6c \(s0f98a\)
HPE Aruba Cx 10040 \(s4r58a\)
HPE Aruba Cx 10040 32p \(s4r54a\)
HPE Aruba Cx 10040 32p \(s4r55a\)
HPE Aruba Cx 10040 32p \(s4r56a\)
HPE Aruba Cx 4100i 12-port \(jl817a\)
HPE Aruba Cx 4100i 24-port \(jl818a\)
HPE Aruba Cx 6000 12g \(r8n89a\)
HPE Aruba Cx 6000 12p \(r8n89b\)
HPE Aruba Cx 6000 12p \(s4r21a\)
HPE Aruba Cx 6000 24g \(r8n87a\)
HPE Aruba Cx 6000 24g \(r8n88a\)
HPE Aruba Cx 6000 24p \(r8n87b\)
HPE Aruba Cx 6000 24p \(r8n88b\)
HPE Aruba Cx 6000 24p \(s4r26a\)
HPE Aruba Cx 6000 24p \(s4r27a\)
HPE Aruba Cx 6000 48g \(r8n85a\)
HPE Aruba Cx 6000 48g \(r8n86a\)
HPE Aruba Cx 6000 48g \(r9y03a\)
HPE Aruba Cx 6000 48p \(r8n85b\)
HPE Aruba Cx 6000 48p \(r8n86b\)
HPE Aruba Cx 6000 48p \(r9y03b\)
HPE Aruba Cx 6000 48p \(s4r20a\)
HPE Aruba Cx 6000 48p \(s4r24a\)
HPE Aruba Cx 6000 48p \(s4r25a\)
HPE Aruba Cx 6000 8p \(s4r22a\)
HPE Aruba Cx 6000 8p \(s4r23a\)
HPE Aruba Cx 6000 8p \(s4r28a\)
HPE Aruba Cx 6000 8p \(s4r29a\)
HPE Aruba Cx 6100 12g \(jl679a\)
HPE Aruba Cx 6100 24g \(jl677a\)
HPE Aruba Cx 6100 24g \(jl678a\)
HPE Aruba Cx 6100 48g \(jl675a\)
HPE Aruba Cx 6100 48g \(jl676a\)
HPE Aruba Cx 6100 48g \(r9y04a\)
HPE Aruba Cx 6200f 12g \(r8q72a\)
HPE Aruba Cx 6200f 12g \(r8v13a\)
HPE Aruba Cx 6200f 24g \(jl724b\)
HPE Aruba Cx 6200f 24g \(jl725b\)
HPE Aruba Cx 6200f 24g \(s0g13a\)
HPE Aruba Cx 6200f 24g \(s0g14a\)
HPE Aruba Cx 6200f 24g \(s0m81a\)
HPE Aruba Cx 6200f 24g \(s0m82a\)
HPE Aruba Cx 6200f 24g \(s0m86a\)
HPE Aruba Cx 6200f 24g \(s0m87a\)
HPE Aruba Cx 6200f 48g \(jl726b\)
HPE Aruba Cx 6200f 48g \(jl727b\)
HPE Aruba Cx 6200f 48g \(jl728b\)
HPE Aruba Cx 6200f 48g \(s0g15a\)
HPE Aruba Cx 6200f 48g \(s0g16a\)
HPE Aruba Cx 6200f 48g \(s0g17a\)
HPE Aruba Cx 6200f 48g \(s0m83a\)
HPE Aruba Cx 6200f 48g \(s0m84a\)
HPE Aruba Cx 6200f 48g \(s0m85a\)
HPE Aruba Cx 6200f 48g \(s0m88a\)
HPE Aruba Cx 6200f 48g \(s0m89a\)
HPE Aruba Cx 6200f 48g \(s0m90a\)
HPE Aruba Cx 6200m 24g \(r8q67a\)
HPE Aruba Cx 6200m 24g \(r8q68a\)
HPE Aruba Cx 6200m 24g \(r8v08a\)
HPE Aruba Cx 6200m 24g \(r8v09a\)
HPE Aruba Cx 6200m 36g \(r8q71a\)
HPE Aruba Cx 6200m 36g \(r8v12a\)
HPE Aruba Cx 6200m 48g \(r8q69a\)
HPE Aruba Cx 6200m 48g \(r8q70a\)
HPE Aruba Cx 6200m 48g \(r8v10a\)
HPE Aruba Cx 6200m 48g \(r8v11a\)
HPE Aruba Cx 6300f 24 \(jl666a\)
HPE Aruba Cx 6300f 24 \(jl668a\)
HPE Aruba Cx 6300f 24p \(s0g96a\)
HPE Aruba Cx 6300f 24p \(s0g98a\)
HPE Aruba Cx 6300f 48 \(jl665a\)
HPE Aruba Cx 6300f 48 \(jl667a\)
HPE Aruba Cx 6300f 48p \(s0g95a\)
HPE Aruba Cx 6300f 48p \(s0g97a\)
HPE Aruba Cx 6300m 16p \(s4p41a\)
HPE Aruba Cx 6300m 16p \(s4p45a\)
HPE Aruba Cx 6300m 24 \(jl658a\)
HPE Aruba Cx 6300m 24 \(jl660a\)
HPE Aruba Cx 6300m 24 \(jl662a\)
HPE Aruba Cx 6300m 24 \(jl664a\)
HPE Aruba Cx 6300m 24p \(r8s89a\)
HPE Aruba Cx 6300m 24p \(r8s92a\)
HPE Aruba Cx 6300m 24p \(s0f99a\)
HPE Aruba Cx 6300m 24p \(s0g01a\)
HPE Aruba Cx 6300m 24p \(s0g03a\)
HPE Aruba Cx 6300m 24p \(s0g05a\)
HPE Aruba Cx 6300m 24p \(s4p44a\)
HPE Aruba Cx 6300m 24p \(s4p48a\)
HPE Aruba Cx 6300m 24p \(s5z46a\)
HPE Aruba Cx 6300m 32p \(s4p42a\)
HPE Aruba Cx 6300m 32p \(s4p46a\)
HPE Aruba Cx 6300m 48 \(jl659a\)
HPE Aruba Cx 6300m 48 \(jl661a\)
HPE Aruba Cx 6300m 48 \(jl663a\)
HPE Aruba Cx 6300m 48 \(jl762a\)
HPE Aruba Cx 6300m 48p \(r8s90a\)
HPE Aruba Cx 6300m 48p \(s0g00a\)
HPE Aruba Cx 6300m 48p \(s0g02a\)
HPE Aruba Cx 6300m 48p \(s0g04a\)
HPE Aruba Cx 6300m 48p \(s0g06a\)
HPE Aruba Cx 6300m 48p \(s0x44a\)
HPE Aruba Cx 6300m 48p \(s4p43a\)
HPE Aruba Cx 6300m 48p \(s4p47a\)
HPE Aruba Cx 6300m 48sr5 \(r8s91a\)
HPE Aruba Cx 6405 \(r0x26a\)
HPE Aruba Cx 6405 48sfp\+8sfp56 \(r0x30a\)
HPE Aruba Cx 6405 96g \(r0x29a\)
HPE Aruba Cx 6405 V2 \(r0x26c\)
HPE Aruba Cx 6410 \(r0x27a\)
HPE Aruba Cx 6410 96g \(jl741a\)
HPE Aruba Cx 6410 V2 \(r0x27c\)
HPE Aruba Cx 8320 32 \(jl579a\)
HPE Aruba Cx 8320 48 \(jl479a\)
HPE Aruba Cx 8320 48 \(jl581a\)
HPE Aruba Cx 8325-32c \(jl626a\)
HPE Aruba Cx 8325-32c \(jl627a\)
HPE Aruba Cx 8325-48y8c \(jl624a\)
HPE Aruba Cx 8325-48y8c \(jl625a\)
HPE Aruba Cx 8325-48y8c \(jl858a\)
HPE Aruba Cx 8325h-16c \(s4b22a\)
HPE Aruba Cx 8325h-16c \(s4b24a\)
HPE Aruba Cx 8325h-18y4c \(s4b21a\)
HPE Aruba Cx 8325h-18y4c \(s4b23a\)
HPE Aruba Cx 8325p-32c \(s0g07a\)
HPE Aruba Cx 8325p-32c \(s0g08a\)
HPE Aruba Cx 8360-12c \(jl708c\)
HPE Aruba Cx 8360-12c \(jl709c\)
HPE Aruba Cx 8360-16y2c \(jl702c\)
HPE Aruba Cx 8360-16y2c \(jl703c\)
HPE Aruba Cx 8360-24xf2c \(jl710c\)
HPE Aruba Cx 8360-24xf2c \(jl711c\)
HPE Aruba Cx 8360-32y4c \(jl700c\)
HPE Aruba Cx 8360-32y4c \(jl701c\)
HPE Aruba Cx 8360-48xt4c \(jl706c\)
HPE Aruba Cx 8360-48xt4c \(jl707c\)
HPE Aruba Cx 8360-48y6c \(jl704c\)
HPE Aruba Cx 8360-48y6c \(jl705c\)
HPE Aruba Cx 8400 \(jl376a\)
HPE Aruba Cx 8400 8-slot Chassis \(jl375a\)
HPE Aruba Cx 9300 \(r8z97a\)
HPE Aruba Cx 9300 \(r8z98a\)
HPE Aruba Cx 9300 \(r8z99a\)
HPE Aruba Cx 9300 \(r9a00a\)
HPE Aruba Cx 9300 32d \(r8z96a\)
HPE Aruba Cx 9300 32d \(r9a29a\)
HPE Aruba Cx 9300 32d \(r9a30a\)
HPE Aruba Cx 9300s 32p \(s0f81a\)
HPE Aruba Cx 9300s 32p \(s0f82a\)
HPE Aruba Cx 9300s 32p \(s0f83a\)
HPE Aruba Cx 9300s 32p \(s0f84a\)
HPE Aruba Cx 9300s 32p \(s0f87a\)
HPE Aruba Cx 9300s 32p \(s0f88a\)
Remediation
Event History
Sep 1, 2026
CVE Published
via MITRE·08:28 PM
Data Sourced
via MITRE·08:28 PM
DescriptionSeverity
Data Sourced
via NVD·09:18 PM
RemedyDescriptionSeverityWeaknessAffected Software
Frequently Asked Questions
1
Who can exploit this issue?
Exploitation requires an authenticated malicious actor with administrative privileges on the AOS-CX command line interface. It is therefore primarily relevant where administrative access has been granted to untrusted or compromised users.
2
What additional conditions are required for exploitation?
Certain pre-conditions outside the attacker’s control must be met. The available information does not identify those conditions, so administrators should consult the vendor advisory to determine whether their environment meets them.
3
What is the potential impact if exploitation succeeds?
A successful attacker could bypass signature verification and execute arbitrary code on the underlying operating system. The published vector indicates high confidentiality and integrity impact, with no stated availability impact.