Skip to main content
CVE-2025-37147VulnerabilityPublished

CVE-2025-37147: Hewlett Packard Enterprise (HPE) ArubaOS (AOS) · Vulnerability

Affects Hewlett Packard Enterprise (HPE) ArubaOS (AOS)Source CVE Database V5

0

Not known to be exploited · CVSS 7.1 High.

Data as of 25 Oct 2026, 19:02 UTC

CVSS 3.1 base score
7.1High
How severe the flaw is on the 0–10 CVSS scale.
EPSS
0.1% chance of exploitation in 30 days – higher than 4% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
CVSS:3.1/AV:L/AC:L/PR:N/UI:N/S:C/C:N/I:H/A:N

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 14 Oct 2025

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponised: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq 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

ProductAffectedFixed in
Hewlett Packard Enterprise (HPE) ArubaOS (AOS)Affected
  • =10.7.0.0
  • =10.4.0.0
  • =8.13.0.0
  • =8.12.0.0
  • =8.10.0.0
Fixed in–

AI-suggested

1. Apply vendor patches immediately once they become available to address the Secure Boot bypass vulnerability. 2. Restrict physical and network access to ArubaOS Access Points, especially management interfaces, to trusted personnel and networks only. 3. Implement network segmentation to limit the exposure of vulnerable Access Points and reduce the attack surface. 4. Employ strict access controls and monitoring on local network segments where Access Points reside to detect unauthorized access attempts. 5. Use hardware security modules or trusted platform modules (TPMs) where possible to enhance device integrity verification. 6. Regularly audit firmware versions and verify cryptographic signatures to detect unauthorized firmware changes. 7. Deploy network intrusion detection systems (NIDS) and anomaly detection tools to identify unusual device behavior indicative of firmware compromise. 8. Maintain an incident response plan that includes procedures for firmware compromise scenarios. 9. Educate IT staff on the risks of firmware-level attacks and the importance of physical security for network devices. 10. Engage with HPE support and subscribe to security advisories to stay informed about updates and patches.

Description

A Secure Boot Bypass Vulnerability exists in affected Access Points that allows an adversary to bypass the hardware root of trust verification in place to ensure only vendor-signed firmware can execute on the device. An adversary can exploit this vulnerability to run modified or custom firmware on affected Access Points.

References

Community reviews

Loading reviews…