CVE-2025-37139: Hewlett Packard Enterprise (HPE) ArubaOS (AOS) · Vulnerability
Affects Hewlett Packard Enterprise (HPE) ArubaOS (AOS)Source CVE Database V5
Not known to be exploited · CVSS 6.0 Medium.
Data as of 25 Oct 2026, 19:02 UTC
- EPSS
- 0.1% chance of exploitation in 30 days – higher than 3% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
CVSS:3.1/AV:L/AC:L/PR:H/UI:N/S:C/C:N/I:N/A:HExploitation evidence
Disclosed: evidence found.
CVE published 14 Oct 2025
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: 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 2026-10-25.
What to do
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| Hewlett Packard Enterprise (HPE) ArubaOS (AOS) | Affected
| Fixed in– |
AI-suggested
1. Enforce strict access control policies limiting privileged access to ArubaOS devices only to trusted administrators. 2. Implement multi-factor authentication (MFA) for all administrative accounts to reduce the risk of credential compromise. 3. Monitor and audit all privileged user activities on ArubaOS devices to detect unusual or unauthorized actions promptly. 4. Segment network management interfaces to restrict access to ArubaOS devices from only secure and monitored networks. 5. Regularly back up device configurations and maintain an inventory of affected ArubaOS versions to prioritize patching. 6. Coordinate with Hewlett Packard Enterprise for timely receipt and deployment of firmware patches or updates addressing this vulnerability. 7. Develop and test incident response plans that include procedures for hardware replacement and network recovery in case of exploitation. 8. Educate administrators about the risks of this vulnerability and the importance of safeguarding privileged credentials. 9. Consider deploying network anomaly detection systems to identify potential exploitation attempts targeting ArubaOS devices. 10. Limit physical access to network hardware to prevent direct tampering that could facilitate exploitation.
Description
A vulnerability in an AOS firmware binary allows an authenticated malicious actor to permanently delete necessary boot information. Successful exploitation may render the system unbootable, resulting in a Denial of Service that can only be resolved by replacing the affected hardware.