HPE has released AOS-8 and AOS-10 updates for its wireless controllers, gateways, conductors and access points. Its October 22 bulletin describes flaws that can give unauthenticated attackers administrative access or code execution on affected devices.
The practical job is to check the software running across the fleet. HPE warns that the bulletin’s hardware examples are incomplete: compatible devices and virtual machines can be affected even when their model is absent.
Match the installed release line to its fix
HPE lists these affected versions and corresponding updates in both the bulletin and its text edition:
| Release line | Affected versions in that line | Fixed version or later in that line |
|---|---|---|
| AOS-10.8.x.x | 10.8.1.1 and below | 10.8.1.2 |
| AOS-10.7.x.x | 10.7.2.6 and below | 10.7.2.7 |
| AOS-10.4.x.x | 10.4.1.13 and below | 10.4.1.14 |
| AOS-8.13.x.x | 8.13.3.0 and below | 8.13.3.1 |
| AOS-8.10.x.x | 8.10.0.23 and below | 8.10.0.24 |
The affected product families include Mobility Conductors, Mobility Controllers, Central-managed Mobility Gateways, AOS-10 access points and AOS-8 Instant access points. Individual vulnerability descriptions can narrow applicability.
Older unsupported releases need separate attention. HPE presumes end-of-maintenance versions affected unless explicitly excluded. It has not assessed end-of-support releases and says to treat them as potentially affected, then move to supported software.
Network access and prerequisites differ by flaw
The bulletin covers 72 CVE identifiers. Sergiu Gatlan’s October 23 report highlights eight with the maximum severity score. That score describes potential impact, not observed attacks or compromised-device counts.
Two examples explain why administrators should prioritize the updates:
- CVE-2026-79850: an unauthenticated attacker reaching the affected AOS-8 interface could bypass authentication and run commands as root, the system’s most privileged account.
- CVE-2026-79845: authentication flaws in PAPI, Aruba’s access-point management protocol, could grant administrative access and allow configuration or sensitive-data changes on AOS-10.
Exposure is not identical across the bundle. Other flaws require an adjacent network position, existing privileges or physical access. CVE-2026-79844, an AOS-10 remote-code-execution issue, also requires preconditions outside the attacker’s control that the bulletin does not fully specify.
Patch, restrict management access, and retain logs
- Inventory running software, including access points and virtual controllers. Match the installed release line to HPE’s table rather than relying on a short hardware list.
- Deploy the applicable fixed release through HPE’s supported upgrade process. Confirm the running version afterward. Software downloads are available through the HPE Networking Support Portal.
- Restrict command-line and web management interfaces while arranging upgrades. HPE recommends a dedicated management network segment, firewall controls, and activity logging.
- Keep patching and exposure reduction separate. A management firewall reduces reachable paths; it does not repair the software or address every adjacent-access flaw in this bundle.
Evidence status: vendor-disclosed vulnerabilities; the reviewed sources do not establish exploitation in the wild. HPE says it knew of no public discussion or exploit code targeting these flaws when it released the bulletin. Most findings came from its internal research, with some credited to external reporters.
Caveat: HPE is both the affected vendor and the main technical source; its release-time knowledge is not proof that exploitation has never occurred.