Skip to main content
CVE-2025-37134VulnerabilityPublished Updated

CVE-2025-37134: Hewlett Packard Enterprise (HPE) ArubaOS (AOS) · Command Injection

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

0

Not known to be exploited · CVSS 7.2 High.

Data as of 25 Oct 2026, 19:02 UTC

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

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

To mitigate CVE-2025-37134, organizations should implement the following specific measures: 1) Immediately restrict CLI access to ArubaOS Controllers and Mobility Conductors to trusted administrators only, using strong authentication methods such as multi-factor authentication (MFA). 2) Enforce the principle of least privilege by limiting user roles and permissions to minimize the number of accounts with high-level CLI access. 3) Monitor and audit CLI command usage and login activity for anomalous behavior indicative of exploitation attempts. 4) Segment network management interfaces from general user networks to reduce exposure. 5) Apply any vendor-released patches or firmware updates as soon as they become available. 6) If patches are not yet available, consider temporary compensating controls such as disabling unused CLI features or restricting access via firewall rules. 7) Conduct regular vulnerability assessments and penetration tests focused on network infrastructure devices to detect potential exploitation. 8) Maintain updated incident response plans that include procedures for network device compromise scenarios.

Description

An authenticated command injection vulnerability exists in the CLI binary of an AOS-8 Controller/Mobility Conductor operating system. Successful exploitation could allow an authenticated malicious actor to execute arbitrary commands as a privileged user on the underlying operating system.

References

Community reviews

Loading reviews…