AOS-CX: authenticated path traversal vulnerability exists in AOS-CX
Summary
An authenticated path traversal vulnerability exists in AOS-CX. Successful exploitation of this vulnerability allows an attacker to copy arbitrary files to a user readable location from the command line interface of the underlying operating system, which could lead to remote code execution.
What this means
In plain English
An authenticated path traversal vulnerability exists in AOS-CX. Successful exploitation of this vulnerability allows an attacker to copy arbitrary files to a user readable location from the command line interface of the underlying operating system, which could lead to remote code execution. Successful exploitation can let an attacker run code in the security context of the affected service or device.
Recommended action
Primary action: update to a vendor-listed fixed release: 10.18.0001. Vendor mitigation: Upgrade affected HPE Aruba Networking devices to an applicable fixed release: AOS-CX 10.17.1021 or above, AOS-CX 10.16.1051 or above, AOS-CX 10.13.1180 or above, AOS-CX 10.18.0001 or above. To address the vulnerabilities described above in the affected software branches, it is recommended to upgrade HPE Networking AOS-CX to one of the following versions (as applicable): - AOS-CX 10.18.xxxx: AOS-CX 10.18.0001 and above - AOS-CX 10.17.xxxx: AOS-CX 10.17.1021 and above - AOS-CX 10.16.xxxx: AOS-CX 10.16.1050 and above - AOS-CX 10.13.xxxx: AOS-CX 10.13.1180 and above Software versions with resolution/fixes for the vulnerabilities covered above can be downloaded from the HPE Networking Support Portal at NOTE: CVE-2026-63454 is resolved in AOS-CX 10.13.1190. Customers running this software branch that are…
Rewritten locally from the scraped official advisory data above; no generative API is used. The vendor advisory is authoritative.
- AOS-CX 10.17.0000 through 10.17.1020
- AOS-CX 10.16.0000 through 10.16.1050
- AOS-CX 10.13.0000 through 10.13.1180
- AOS-CX 10.18.0000 before 10.18.0001
Official advisory · high-confidence parse· fetched 4 hours ago·verify at source
- 10.18.0001
Official advisory · high-confidence parse· fetched 4 hours ago·verify at source
Mitigation checklist
- Upgrade affected HPE Aruba Networking devices to an applicable fixed release: AOS-CX 10.17.1021 or above, AOS-CX 10.16.1051 or above, AOS-CX 10.13.1180 or above, AOS-CX 10.18.0001 or above.
- To address the vulnerabilities described above in the affected software branches, it is recommended to upgrade HPE Networking AOS-CX to one of the following versions (as applicable): - AOS-CX 10.18.xxxx: AOS-CX 10.18.0001 and above - AOS-CX 10.17.xxxx: AOS-CX 10.17.1021 and above - AOS-CX 10.16.xxxx: AOS-CX 10.16.1050 and above - AOS-CX 10.13.xxxx: AOS-CX 10.13.1180 and above Software versions with resolution/fixes for the vulnerabilities covered above can be downloaded from the HPE Networking Support Portal at https://networkingsupport.hpe.com/home/ NOTE: CVE-2026-63454 is resolved in AOS-CX 10.13.1190. Customers running this software branch that are unable to upgrade to a newer software branch are advised to use the available workaround until this resolved version becomes publicly available. HPE Aruba Networking does not evaluate or patch software branches that have reached their End of Maintenance (EoM) milestone. For more information about HPE Aruba Networking End of Life policy please visit: https://www.hpe.com/psnow/doc/a00143052enw
- To minimize the likelihood of an attacker exploiting this vulnerability, HPE Aruba Networking recommends that the `copy` command be restricted until the vulnerable system can be safely upgraded. Additionally, HPE Aruba Networking recommends that management interfaces be restricted to a dedicated layer 2 segment/VLAN and/or controlled by firewall policies at layer 3 and above, along with accounting controls for tracking and logging user activities and resource usage.
Official advisory · high-confidence parse· fetched 4 hours ago·verify at source
Discussion(0)
No comments yet. Share field notes, upgrade gotchas, or questions — verify against the vendor advisory before acting on community advice.
Sign in to join the discussion.