Published 19 November 2026 · Rathish Kumar, Invitty

HPE revised its Aruba wireless bulletin HPESBNW05162 on 17 November 2026. It now lists 76 vulnerabilities in AOS-8 and AOS-10, the software that runs Aruba Mobility Conductors, Controllers, Gateways and access points, and eight of them score the maximum CVSS 10.0. If you run AOS-10 up to 10.8.1.1 or AOS-8 up to 8.13.3.0, upgrade to a fixed build: 10.8.1.2, 10.7.2.7, 10.4.1.14, 8.13.3.1 or 8.10.0.24.

What changed in the 17 November revision

The bulletin first came out on 22 October 2026 with 72 CVEs. Revision 2 does two things. First, HPE corrected the CVE list: CVE-2026-79845 was replaced by CVE-2026-95787, and four entries that HPE says were left out by an editorial error were added (CVE-2026-95788 to CVE-2026-95791). Second, it added a note for FIPS customers. If you run AP-5xx series access points in a FIPS-compliant deployment, the minimum build is now AOS 8.13.3.2 FIPS, not 8.13.3.1.

So if your team patched in late October, you are probably fine on the code. What you should recheck is the FIPS line, and whether your vulnerability scanner has picked up the corrected CVE numbers. A scanner that still reports CVE-2026-79845 is working from the old list.

Which Aruba devices and AOS versions are affected?

The bulletin covers Mobility Conductors, Mobility Controllers, Mobility Gateways managed by HPE Networking Central, AOS-10 access points and AOS-8 Instant access points. HPE states that products and versions it does not list are not affected, which means Aruba CX switches running AOS-CX are outside this bulletin.

HPESBNW05162: affected and fixed AOS buildsScroll sideways to see the full table
Software trainAffectedUpgrade to
AOS-10.810.8.1.1 and below10.8.1.2 or later
AOS-10.710.7.2.6 and below10.7.2.7 or later
AOS-10.410.4.1.13 and below10.4.1.14 or later
AOS-8.138.13.3.0 and below8.13.3.1 or later
AOS-8.13 FIPS (AP-5xx)Builds before 8.13.3.2 FIPS8.13.3.2 FIPS or later
AOS-8.108.10.0.23 and below8.10.0.24 or later

To check what you run, open the controller or Conductor web UI and look at the dashboard, or run show version on the CLI. On Instant APs the virtual controller shows the build under Maintenance. In Central, the firmware page lists every gateway and AP with its current version.

One gap: the bulletin names only five trains. If a controller still runs something older, such as an 8.6 or 8.11 build, do not read its absence as good news. Ask HPE support, or us, before assuming it is safe.

How serious is it, and is anyone exploiting it?

By our count of the revised bulletin, 33 of the 76 CVEs score 9.0 or higher. Most are unauthenticated: command injection, SQL injection, buffer overflows and authentication bypasses in the web management interface, the SSH daemon and PAPI, the protocol Aruba devices use to talk to each other. A large group is marked "adjacent", which means the attacker needs to be on the same network segment. On a wireless network, that can include a guest or a contractor on the Wi-Fi.

HPE says its own researchers found these issues and that it knew of no public discussion or exploit code when it released the bulletin. None of the CVEs appear in CISA's Known Exploited Vulnerabilities catalogue as of the 18 November 2026 version. That is the good news. The less good news is that a list of 76 flaws, with an advisory that names the vulnerable component for each, is a useful map for anyone writing an exploit. We would not wait for the first report of attacks.

What to do, in order

  1. Inventory. List every Conductor, controller, gateway and Instant AP cluster with its current AOS build. Note any AP-5xx units in FIPS mode.
  2. Restrict management now. HPE's workaround is to keep the CLI and web management interfaces on a dedicated layer 2 segment or VLAN, or behind firewall rules at layer 3 and above, with accounting turned on. If your controller management IP is reachable from the user or guest VLAN, fix that today. It costs nothing.
  3. Plan the upgrade. Download the fixed build for your train from the HPE Networking Support Portal. For controller clusters, upgrade the Conductor first, then the managed devices, and pre-load the AP image so the APs do not all pull it at once.
  4. Schedule a window. Controllers and APs reboot during the upgrade, so Wi-Fi drops. Pick an evening or a Sunday slot and tell users.
  5. Verify and record. Confirm the new build on every device, rescan, and keep a note of the date for your audit file.

What it means for Aruba owners in India

Check your support contract before the maintenance window, because the fixed builds come from the HPE Networking Support Portal. If a controller has fallen out of support, this is a good moment to price the renewal against moving those sites to AOS-10 or Central-managed APs, and to put the figure in next quarter's budget with a GST invoice behind it.

If you find signs that a controller was tampered with, remember that CERT-In expects certain cyber incidents to be reported within 6 hours of noticing them. Keep logs from the controller and the upstream firewall before you rebuild anything. Where guests share the Wi-Fi with staff, guest VLAN separation matters more than usual this month.

Next step

We deploy and support Aruba wireless for offices, campuses and warehouses across South India. Send us your controller models, AP count and current AOS build, and we will tell you which fixed release fits your train, whether your AP-5xx units need the FIPS build, and what the upgrade window looks like. See our Aruba page and Aruba access points for hardware and licences, or renewals if your support contract needs attention.

Questions about the Aruba AOS bulletin

Which Aruba AOS versions fix HPESBNW05162?
HPE lists AOS 10.8.1.2, 10.7.2.7 and 10.4.1.14 for AOS-10, and 8.13.3.1 and 8.10.0.24 for AOS-8. Customers running AP-5xx access points in a FIPS-compliant setup need AOS 8.13.3.2 FIPS or later. Later builds on the same train also include the fixes.
Are the Aruba AOS flaws being exploited?
HPE said it knew of no public discussion or exploit code when it released the bulletin, and none of the CVEs were in CISA's Known Exploited Vulnerabilities catalogue as of 18 November 2026. That can change quickly once a fix list is public, so treat the upgrade as urgent.
Are Aruba CX switches affected?
No. The bulletin covers AOS-8 and AOS-10 on Mobility Conductors, Controllers, Gateways and access points, and HPE says products not listed are not affected. Aruba CX switches run AOS-CX, which is a separate operating system.
What can we do if we cannot upgrade this week?
Follow HPE's workaround. Keep the CLI and web management interfaces on a dedicated management VLAN or behind firewall rules, and turn on accounting so you can see who logs in. Then book the upgrade, because the workaround does not cover every flaw.

Not sure if your devices are affected? Send us the model and current firmware or version on WhatsApp, or use the form on this page. We will tell you whether this advisory applies to you and which update to schedule.

Sources

Facts in this post come from these pages, checked on 19 November 2026. HPE revises its bulletins, so confirm fixed builds on the HPE support portal before you upgrade.