Introduction
A set of authentication bypass flaws in the PAPI protocol of HPE AOS 10 lets an unauthenticated remote attacker circumvent the controls that are supposed to gate access. The CVE record lists administrative access, configuration changes, and access to or manipulation of sensitive data as possible outcomes. HPE scored the issue CVSS 3.1 10.0. The fix shipped in October under a different CVE ID, so some teams are already covered without knowing it, while others may be tracking the wrong identifier.
AOS 10 (ArubaOS) is the operating system behind HPE Aruba Networking wireless infrastructure, running on Mobility Conductors, Mobility Controllers, Central managed Mobility Gateways and access points. HPE positions Aruba Networking as secure networking from edge to cloud. The sources we reviewed do not quantify its market share. Because AOS 10 runs the controllers, gateways and access points that make up an enterprise wireless deployment, a flaw in one of its internal control protocols touches core network infrastructure rather than a single application.
Technical information
What the record says
The CVE record, published by HPE as CNA on 18 November 2026, states that vulnerabilities in the PAPI protocol of AOS 10 could allow an unauthenticated remote attacker to circumvent existing authentication controls. Successful exploitation could allow an attacker to gain administrative access, modify system configurations, and access or manipulate sensitive data. The record credits internal security research from HPE Networking.
Root cause
HPE has not described the code change, and AOS 10 is closed source, so there is no public commit, diff or vulnerable code snippet to examine. What the bulletin does tell us:
- CVE-2026-95787 is six bugs. It bundles six internal tracking IDs: VULN-1126, VULN-1264, VULN-1266, VULN-1268, VULN-1273 and VULN-1277. They are a group of authentication bypass flaws in PAPI, fixed together in the same releases.
- The weakness is in PAPI authentication. HPE's wording, that an attacker can "circumvent existing authentication controls" in PAPI, indicates that AOS 10 could be induced to act on PAPI messages without properly verifying that they were authenticated. The exact checks that failed, and how each of the six issues differs, have not been disclosed.
- The record does not supply a CWE, and we are not inferring one.
CVSS vector
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:H/A:N
In plain terms: the attack is network based (AV:N), requires low complexity (AC:L), needs no privileges (PR:N) and no user interaction (UI:N). The scope is changed (S:C), meaning the impact extends beyond the vulnerable component itself. Confidentiality and integrity impacts are high, and the scored vector records no availability impact.
Attack flow
Based only on what HPE has published, the attack looks like this:
- The attacker has network reachability to the PAPI service on an affected AOS 10 device. No credentials and no victim interaction are required.
- The attacker sends PAPI traffic that exploits one of the six authentication weaknesses, causing the device to bypass the authentication controls that should reject unauthenticated messages.
- The device acts on that traffic as though it were trusted. Per the record, the result can be administrative access, modification of system configuration, and access to or manipulation of sensitive data.
HPE has not published a request sequence, payload, or protocol-level exploitation details, and no verified proof of concept exists in the sources we reviewed. We are deliberately not filling that gap with speculation.
Exploitation status
OffSeq Threat Radar reported no exploitation in the wild, no public exploit code in Metasploit or Exploit-DB, no CISA KEV listing, and no attack traffic from its sensors, and named no threat actor. That snapshot was taken on 18 November 2026 at 14:20 UTC, very shortly after publication, so treat it as an early observation rather than an assurance.
Patch information
HPE fixed CVE-2026-95787 in new AOS 10 firmware releases. There is no separate hotfix or source patch. The fix is documented only in security bulletin HPESBNW05162.
Fixed builds
Each affected branch has its own fixed build, and upgrading to the next maintenance release on the same branch is sufficient:
- 10.8.x.x: last vulnerable build 10.8.1.1; fixed in 10.8.1.2 and above
- 10.7.x.x: last vulnerable build 10.7.2.6; fixed in 10.7.2.7 and above
- 10.4.x.x: last vulnerable build 10.4.1.13; fixed in 10.4.1.14 and above
The builds are available from the HPE Networking Support Portal (networkingsupport.hpe.com) and apply to the AOS 10 platforms covered by the bulletin: Mobility Conductors, Mobility Controllers, Central managed Mobility Gateways and AOS 10 access points. The bulletin also lists AOS 8 fixes, including a FIPS-specific 8.13.3.2 build for AP 5xx access points, but those address other CVEs and do not change remediation for this one.
Related fixes in the same builds
Because the six underlying issues are fixed together, take the full fixed release rather than looking for a narrower fix. The same builds also close other AOS 10 PAPI flaws:
- CVE-2026-79873, an adjacent-network authentication bypass
- CVE-2026-95716, a lower-severity configuration change bypass
- CVE-2026-79861, a command injection
The CVE ID changed after release
The fix originally shipped on 22 October 2026 in revision 1 of HPESBNW05162, where this flaw was listed as CVE-2026-79845. Revision 2, dated 17 November 2026, states that HPE "Corrected the CVE listing by replacing CVE-2026-79845 with CVE-2026-95787". The CVE record followed on 18 November 2026.
Practical consequences:
- The fixed firmware did not change. Devices already running 10.8.1.2, 10.7.2.7 or 10.4.1.14 (or later) since the October release already have this fix.
- Scanners, patch trackers and earlier news coverage may still reference CVE-2026-79845. Treat both IDs as the same fix when checking coverage.
Versions outside the bulletin
HPE notes that releases past End of Maintenance are presumed affected and are not covered, and releases past End of Support were not assessed. Devices on those versions only receive this fix by moving to a supported branch and its fixed build.
Affected systems and versions
The CVE record lists HPE ArubaOS (AOS 10) as affected in three ranges:
- 10.4.0.0 through 10.4.1.13
- 10.7.0.0 through 10.7.2.6
- 10.8.0.0 through 10.8.1.1
The record sets the product default status to affected and does not itself name an unaffected release. The fixed builds come from bulletin HPESBNW05162. Covered platforms are AOS 10 Mobility Conductors, Mobility Controllers, Central managed Mobility Gateways and AOS 10 access points. Only AOS 10 is listed as affected by this CVE. AOS 10 releases past End of Maintenance are presumed affected, and releases past End of Support were not assessed.
Vendor security history
This CVE arrives as part of a larger bulletin. HPESBNW05162 covers multiple vulnerabilities across AOS 10 and AOS 8, and the same AOS 10 builds address several other PAPI issues (CVE-2026-79873, CVE-2026-95716 and CVE-2026-79861). BleepingComputer covered the release under the headline "HPE patches eight max severity RCE and auth bypass AOS flaws". The finding itself is credited to internal HPE Networking research. Beyond this bulletin, the sources we reviewed are too narrow to draw a broader conclusion about HPE's security track record.
References
- NVD entry for CVE-2026-95787
- CVE Record: CVE-2026-95787
- CVE Services API record for CVE-2026-95787
- HPE Security Bulletin HPESBNW05162
- HPE Networking CSAF advisory HPESBNW05162
- BleepingComputer: HPE patches eight max severity RCE and auth bypass AOS flaws
- OffSeq Threat Radar: CVE-2026-95787
- HPE Aruba Networking product overview



