HPE Aruba AOS 8 and AOS 10: Patch Eight CVSS 10.0 Flaws Now

HPE advisory HPESBNW05162 lists eight CVSS 10.0 flaws in affected AOS-8 and AOS-10 ranges. HPE recommends fixed releases and restricted CLI/web management.

Reader ratingRate this article

Loading reader rating…

Privacy-conscious voting uses a signed random browser identifier and a short-lived network hash; the rating tables contain no raw IP-address column.

Reader ratings require JavaScript; the article remains fully readable without it.

Eight CVSS 10.0 flaws inside a broader wireless-software advisory[1]

HPE Aruba AOS 8 and AOS 10: patch eight maximum-severity flaws now[1]

HPE Networking advisory HPESBNW05162 includes eight CVE records—CVE-2026-79844 through CVE-2026-79851—with CVSS v3.1 base scores of 10.0. They affect specific supported AOS-8 and AOS-10 maintenance ranges used by Mobility Conductors, Mobility Controllers, Central-managed Mobility Gateways, AOS-10 access points and AOS-8 Instant access points.[1][2]

Reporting cutoff: 2026-10-23T15:12:40Z. HPE labels the advisory final, revision 1, published and last updated October 22, 2026. The advisory is broader than these eight entries; this article focuses only on its CVSS 10.0 subset.[1]

Decision

If an in-scope device is on an affected build, plan an urgent supported upgrade. Do not treat management-plane isolation as a substitute for patching: HPE calls it a workaround to minimize likelihood, while its resolution is to upgrade to a fixed release.[1]

Exact exposure predicate

Treat a device as exposed to this eight-CVE subset only when all applicable conditions line up: it runs one of the affected AOS ranges below; it is one of the covered device roles; the affected interface or protocol path can receive attacker-controlled traffic; and, for CVE-2026-79844 or CVE-2026-79846, HPE’s unspecified preconditions outside the attacker’s control are also met. Presence of AOS alone does not prove reachability or successful exploitation.[1][2]

Phone readers: swipe the table left to see every column.

Branch Known affected range in CSAF First listed fixed build
AOS-10 10.8 10.8.0.0–10.8.1.1 10.8.1.2 and above[2]
AOS-10 10.7 10.6.0.0–10.7.2.6 10.7.2.7 and above[2]
AOS-10 10.4 10.3.0.0–10.4.1.13 10.4.1.14 and above[2]
AOS-8 8.13 8.12.0.0–8.13.3.0 8.13.3.1 and above[2]
AOS-8 8.10 8.10.0.0–8.10.0.23 8.10.0.24 and above[2]

Lifecycle caveat: HPE says end-of-maintenance versions are presumed affected unless explicitly excluded, while end-of-support versions were not assessed and should be considered potentially impacted; move those deployments to a supported release rather than assuming an old branch is safe.[1]

The eight maximum-score CVEs

Every score and vector below is CVSS v3.1 from HPE’s live CSAF document.

CVE Product and condition Vendor-described impact Score / vector
CVE-2026-79844 Affected AOS-10 interface; unauthenticated remote attacker; HPE says unspecified preconditions outside the attacker’s control must be met. Arbitrary commands on the host. Authentication Bypass Leading to Remote Code Execution in AOS-10 10.0
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:H/A:N[2]
CVE-2026-79845 AOS-10 PAPI protocol; unauthenticated remote attacker. Authentication bypass can lead to administrative access, configuration changes and sensitive-data access or manipulation. Authentication Bypass Vulnerabilities in the PAPI Protocol of AOS-10 allow Unauthorized Access and Modification of Sensitive Data 10.0
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:H/A:N[2]
CVE-2026-79846 Affected AOS-8 interface; unauthenticated remote attacker; HPE says unspecified preconditions outside the attacker’s control must be met. Arbitrary commands on the host. Unauthenticated Command Injection Vulnerabilities in AOS-8 10.0
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:H/A:H[2]
CVE-2026-79847 Affected AOS-10 interface; unauthenticated specially crafted packets. Privileged arbitrary-code execution. Unauthenticated Buffer Overflow Vulnerabilities leads to Remote Code Execution in AOS-10 10.0
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:H/A:H[2]
CVE-2026-79848 Affected AOS-8 interface; unauthenticated remote SQL injection. Arbitrary commands on the host. Unauthenticated SQL Injection Vulnerabilities allow Remote Code Execution in AOS-8 10.0
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:H/A:H[2]
CVE-2026-79849 Affected AOS-8 interface; unauthenticated remote SQL injection. Arbitrary commands on the host. Unauthenticated SQL Injection Vulnerabilities allow Remote Code Execution in AOS-8 10.0
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:H/A:H[2]
CVE-2026-79850 Affected AOS-8 interface; unauthenticated authentication bypass. Root command execution and complete system compromise. Authentication Bypass Leading to Remote Code Execution in AOS-8 10.0
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:H/A:N[2]
CVE-2026-79851 Affected AOS-10 interface; unauthenticated buffer overflow. Privileged code execution and complete system compromise. Unauthenticated Buffer Overflow Vulnerability leads to Remote Code Execution in AOS-10 10.0
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:H/A:H[2]

Seven of the eight CVE Program records matched HPE’s CVSS v3.1 score and vector at the reporting cutoff. The public record for CVE-2026-79845 did not: it named an unrelated code-projects Simple Inventory System SQL-injection issue, assigned by VulDB, with a 7.3 CVSS v3.1 score. HPE’s CSAF simultaneously assigned CVE-2026-79845 to an AOS-10 PAPI authentication bypass with a 10.0 score. Treat that identifier collision as unresolved metadata, use HPESBNW05162 as the operational patch source, and watch both publishers for correction.[2][3][4][5][6][7][8][9][10][11]

Non-destructive inventory before change

  • Risk-based editorial guidance — inventory: Record, without modifying the device, its role, serial or asset identifier, cluster or HA membership, active AOS train and full four-part running build from a read-only management view or established inventory export.
  • Risk-based editorial guidance — reachability: Document which VLANs, routed networks, VPNs, jump hosts and external paths can reach the web, CLI, PAPI or other affected management or service interfaces.
  • Risk-based editorial guidance — address families: Check IPv4 and IPv6 separately.
  • Scope label: Treat this as an exposure map, not an exploitation test.
  • Risk-based editorial guidance — preservation: Export the current configuration and preserve recent authentication events, configuration-change events, crash events and service-restart events with established read-only tools before rollout.
  • HPE guidance: HPE recommends accounting controls for tracking and logging user activity and resource usage.[1]
  • Risk-based editorial guidance — lifecycle: Flag each end-of-maintenance or end-of-support branch for migration to a supported release.
  • Risk-based editorial guidance — version precision: Compare the full running build, not only the headline branch number.

Prioritized remediation

  1. HPE workaround: Restrict CLI and web management to a dedicated Layer 2 segment or VLAN and/or Layer 3-and-above firewall policy, with accounting controls.[1]
  2. Risk-based editorial guidance — recovery access: Preserve only the administration access needed for controlled maintenance and recovery.
  3. HPE resolution: Upgrade to at least 10.8.1.2, 10.7.2.7, 10.4.1.14, 8.13.3.1 or 8.10.0.24 as appropriate.[1][2]
  4. Risk-based editorial guidance — release selection: Prefer a currently supported release in the chosen train only after checking HPE release notes and hardware support for the exact deployment.
  5. Risk-based editorial guidance — backup: Back up the configuration before rollout.
  6. Risk-based editorial guidance — image: Confirm image provenance and storage headroom before rollout.
  7. Risk-based editorial guidance — canary: Test a representative controller, gateway and access-point set before broad rollout.
  8. Risk-based editorial guidance — recovery: Preserve a recovery path that does not restore an affected build.
  9. Risk-based editorial guidance — deployment scope: Roll the selected fixed release through every in-scope control-plane member and site.
  10. Risk-based editorial guidance — companion nodes: Include standby nodes, managed gateways, controller-cluster members and access points so an affected image does not remain active after the apparent upgrade.

Verification after rollout

  • Risk-based editorial guidance — running build: Re-inventory the running build on every covered device after rollout.
  • HPE threshold reference: The applicable fixed build thresholds are listed in the HPE release table above.[2]
  • Verification limit: A downloaded image or updated manager record does not prove that every node booted the fixed build.
  • Risk-based editorial guidance — service health: Confirm expected HA or cluster health, access-point and gateway adoption, configuration synchronization and normal client or service operation.
  • Risk-based editorial guidance — post-rollout logs: Inspect logs for failed boots, crash loops, repeated restarts and unexpected configuration changes.
  • Verification limit: These checks indicate rollout health, not proof that exploitation never occurred.
  • Risk-based editorial guidance — containment verification: Recheck that web and CLI management remain limited to intended administration paths.
  • Risk-based editorial guidance — telemetry verification: Recheck that logging and accounting still work after the upgrade.
  • Risk-based editorial guidance — residual inventory: Search for forgotten labs, spares, secondary sites and lifecycle-excluded devices.
  • Risk-based editorial guidance — residual containment: Keep isolation in place while any affected build remains.

Exploitation status and uncertainty

As of the advisory’s October 22 release date, HPE said it was not aware of public discussion or exploit code targeting the listed vulnerabilities. That statement is time-bounded and does not establish that exploitation has never occurred.[1]

At this article’s reporting cutoff, none of these eight CVEs appeared in CISA KEV catalog version 2026.10.21, released 2026-10-21T14:04:39.8983Z. Catalog absence is not evidence of no exploitation, and HPE did not publish unique indicators of compromise for this subset in the reviewed advisory.[3][1]

What remains unknown: HPE does not identify the affected interface for several entries and does not describe the external preconditions for CVE-2026-79844 or CVE-2026-79846.[1] The reviewed HPE advisory does not provide a victim count or an in-the-wild exploitation finding.

Risk-based editorial guidance — incident assessment: Do not treat generic crashes, restarts or suspicious traffic as proof of compromise without corroborating evidence.

Bottom line

Risk-based editorial guidance: Inventory exact builds and reachable paths without changing devices.

HPE guidance: Restrict CLI and web management as described in HPE’s workaround and move each affected deployment to an applicable fixed release.[1]

Risk-based editorial guidance: Verify the running build and expected network behavior after rollout.

Risk-based editorial guidance — suspected compromise: Preserve logs and configuration before disruptive cleanup, then use the organization’s incident-response process.

Limit: Installing fixed builds addresses the listed vulnerabilities but does not by itself prove that a device was never accessed.

Sources

  1. HPE Networking — signed text for HPESBNW05162 (official advisory, publication and last update October 22, 2026).
  2. HPE Networking — CSAF 2.0 JSON for HPESBNW05162 (machine-readable affected ranges, fixed releases, CVSS scores and vectors).
  3. CISA — Known Exploited Vulnerabilities catalog JSON (catalog version and bounded identifier check at the reporting cutoff).
  4. CVE Program API record — CVE-2026-79844 (published record checked at the reporting cutoff).
  5. CVE Program API record — CVE-2026-79845 (published record checked at the reporting cutoff).
  6. CVE Program API record — CVE-2026-79846 (published record checked at the reporting cutoff).
  7. CVE Program API record — CVE-2026-79847 (published record checked at the reporting cutoff).
  8. CVE Program API record — CVE-2026-79848 (published record checked at the reporting cutoff).
  9. CVE Program API record — CVE-2026-79849 (published record checked at the reporting cutoff).
  10. CVE Program API record — CVE-2026-79850 (published record checked at the reporting cutoff).
  11. CVE Program API record — CVE-2026-79851 (published record checked at the reporting cutoff).