dbcve.org
ArubaosOperating system · Arubanetworks

CVE-2025-37133

HIGH · 7.2 CVSS v3.1 Published 2025-10-14
Fix available
A fix is available. Upgrade to 8.10.0.19 / 8.12.0.6 or later.
See remediation →
78/100
Remediation priority · High
Remotely reachable Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
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.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · moderate confidence

Authenticated command injection vulnerability in the CLI binary of Aruba AOS-8 Controllers and Mobility Conductors allows attackers with valid CLI credentials to execute arbitrary operating system commands with elevated privileges.

MitigationRestrict CLI access to trusted networks/management VLANs, enforce strong authentication, and apply vendor-provided patches when available. Implement network segmentation to limit exposure.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
ArubaosOperating system
Affected:>= 8.10.0.0, < 8.10.0.19>= 8.12.0.0, < 8.12.0.6>= 8.13.0.0, < 8.13.1.0>= 10.4.0.0, < 10.4.1.9>= 10.7.0.0, < 10.7.2.1

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
High
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:H/I:H/A:H

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Identify the installed AOS version
    Access the Aruba controller CLI or management interface and run the command 'show version' to display the current AOS firmware version
    Affected if The displayed version falls within these ranges: 8.10.0.0 to 8.10.0.18, 8.12.0.0 to 8.12.0.5, 8.13.0.0 to 8.13.0.x (before 8.13.1.0), 10.4.0.0 to 10.4.1.8, or 10.7.0.0 to 10.7.2.0
  2. Verify CLI access method and exposure
    Check the controller management configuration using 'show management' or review the management interface settings to determine if CLI (SSH/Telnet) is enabled and which IP addresses/networks are permitted to access it
    Affected if CLI access is enabled and permitted from networks outside of trusted management VLANs or administration subnets
  3. Confirm management interface network placement
    Review the management VLAN configuration using 'show vlan' or the management interface settings to identify which VLAN or IP range the CLI management interface is bound to
    Affected if The management interface is placed on a VLAN accessible from untrusted or DMZ networks rather than an isolated management VLAN
  4. Check for existing CLI user accounts
    Use 'show user' or review local user database with 'show local-userdb' to enumerate valid CLI accounts configured on the system
    Affected if CLI user accounts exist (the vulnerability requires valid CLI credentials, so any configured CLI user represents potential attack surface)

The environment is affected if the installed AOS version matches any of the affected version ranges AND the CLI interface is accessible from networks outside trusted administration ranges.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Upgrade available Upgrade to 8.10.0.19 / 8.12.0.6 / 8.13.1.0 or later
Fixed in 8.10.0.198.12.0.68.13.1.0
Interim mitigation

Restrict CLI access to trusted networks/management VLANs, enforce strong authentication, and apply vendor-provided patches when available. Implement network segmentation to limit exposure.

Recommended fix High confidence

Upgrade to 8.10.0.19, 8.12.0.6, 8.13.1.0, or 10.4.1.9 (or later) depending on your current branch

  1. 1. Review the current ArubaOS version by running 'show version' in the CLI
  2. 2. Create a backup of the current configuration using 'backup flash' or the WebUI
  3. 3. Download the appropriate fixed version from HPE Aruba support portal (support.hpe.com)
  4. 4. Upload the new firmware image to the controller/conductor
  5. 5. Initiate the upgrade using 'upgrade-software' command or via WebUI
  6. 6. After reboot, verify the new version is running with 'show version'
  7. 7. Confirm functionality and that the vulnerability is addressed
Caveat Standard ArubaOS upgrade - review release notes for any migration considerations from your current version

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Arubaos Scoped from the published advisory
  • Consultation3.0 h
  • Implementation4.0 h
  • Testing3.0 h
  • Review / QA2.0 h
12.0 hours of engineering $2,130
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,408.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2025-37133 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2025-37133 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data