Skip to main content
VulnerabilityPublished Updated

CVE-2025-37133: 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 26 Oct 2026, 10:12 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 26 Oct 2026.

What to do

Affected software

ProductAffectedFixed in
Hewlett Packard Enterprise (HPE) ArubaOS (AOS)Affected
  • 8.10.0.0 – 10.7.0.0
5 affected builds
Fixed in–

AI-suggested

To mitigate CVE-2025-37133, organizations should implement the following specific measures: 1) Immediately restrict CLI access to ArubaOS Controllers and Mobility Conductors to trusted administrators only, using network segmentation and access control lists. 2) Enforce strong authentication mechanisms, such as multi-factor authentication (MFA), to reduce the risk of credential compromise. 3) Monitor CLI access logs and network traffic for unusual command execution patterns or unauthorized access attempts. 4) Apply principle of least privilege by limiting administrative roles and permissions to only those necessary. 5) Stay alert for official patches or updates from Hewlett Packard Enterprise and plan prompt deployment once available. 6) Consider deploying compensating controls such as network-based intrusion detection/prevention systems (IDS/IPS) tuned to detect command injection attempts. 7) Conduct regular security audits and penetration tests focusing on ArubaOS devices to identify potential exploitation attempts. 8) Educate administrators on secure CLI usage and the risks of command injection vulnerabilities.

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…