CVE-2026-23808: Hewlett Packard Enterprise (HPE) HPE Aruba Networking Wireless Operating System (AOS-10 & AOS-8) · Code Injection
Affects Hewlett Packard Enterprise (HPE) HPE Aruba Networking Wireless Operating System (AOS-10 & AOS-8)Source CVE Database V5
Not known to be exploited · CVSS 5.4 Medium.
Data as of 30 Oct 2026, 11:52 UTC
- EPSS
- 0.2% chance of exploitation in 30 days – higher than 18% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
CVSS:3.1/AV:A/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:NExploitation evidence
Disclosed: evidence found.
CVE published 4 Mar 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors
A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 30 Oct 2026.
What to do
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| Hewlett Packard Enterprise (HPE)HPE Aruba Networking Wireless Operating System (AOS-10 & AOS-8) | Affected
| Fixed in– |
AI-suggested
- Monitor HPE Aruba Networks advisories closely for official patches addressing CVE-2026-23808 and apply them promptly to all affected AOS versions.
- Until patches are available, implement strict wireless network segmentation and enforce client isolation policies at the network level to limit the impact of unauthorized frame injection.
- Use wireless intrusion detection and prevention systems (WIDS/WIPS) to monitor for anomalous frame injection or unusual roaming behavior indicative of exploitation attempts.
- Restrict physical and logical access to wireless infrastructure to trusted personnel and devices to reduce the attack surface.
- Employ strong authentication and encryption protocols (e.g., WPA3) to enhance wireless security beyond the vulnerable protocol.
- Conduct regular security assessments and penetration tests focusing on wireless network security to identify and remediate weaknesses.
- Educate network administrators about the risks of this vulnerability and the importance of timely patching and monitoring.
- Consider deploying network access control (NAC) solutions to enforce device compliance and isolate suspicious clients. These measures, combined with patching, will help mitigate the risk posed by this vulnerability effectively.
Description
A vulnerability has been identified in a standardized wireless roaming protocol that could enable a malicious actor to install an attacker-controlled Group Temporal Key (GTK) on a client device. Successful exploitation of this vulnerability could allow a remote malicious actor to perform unauthorized frame injection, bypass client isolation, interfere with cross-client traffic, and compromise network segmentation, integrity, and confidentiality.