Skip to main content
CVE-2025-37161VulnerabilityPublished

CVE-2025-37161: Hewlett Packard Enterprise (HPE) HPE Aruba Networking 100 Series Cellular Bridge · Vulnerability

Affects Hewlett Packard Enterprise (HPE) HPE Aruba Networking 100 Series Cellular BridgeSource CVE Database V5

0

Not known to be exploited · CVSS 7.5 High.

Data as of 25 Oct 2026, 19:02 UTC

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

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 18 Nov 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) HPE Aruba Networking 100 Series Cellular BridgeAffected
  • =10.7.0.0
Fixed in–

AI-suggested

1. Immediately restrict access to the web-based management interface of the affected HPE Aruba 100 Series Cellular Bridge devices by implementing network segmentation and firewall rules limiting management traffic to trusted IP addresses only. 2. Monitor HPE advisories closely for the release of official patches or firmware updates addressing CVE-2025-37161 and apply them promptly once available. 3. Implement network intrusion detection/prevention systems (IDS/IPS) to detect and block suspicious traffic patterns targeting the management interface. 4. Employ strong network access controls and consider disabling the web management interface if remote management is not required or use alternative secure management methods such as VPNs or out-of-band management. 5. Develop and test incident response procedures to quickly identify and recover from denial of service events caused by this vulnerability, including manual reboot protocols. 6. Conduct regular vulnerability assessments and penetration testing focusing on network devices to identify similar weaknesses proactively. 7. Educate network operations teams about this vulnerability and the importance of monitoring device health and logs for signs of exploitation attempts.

Description

A vulnerability in the web-based management interface of affected products could allow an unauthenticated remote attacker to cause a denial of service. Successful exploitation could allow an attacker to crash the system, preventing it from rebooting without manual intervention and disrupting network operations.

References

Community reviews

Loading reviews…