ArubaosOperating system · Arubanetworks

CVE-2025-37170

HIGH · 7.2 CVSS v3.1 Published 2026-01-13
Fix available
A fix is available. Upgrade to 8.10.0.21 / 8.13.1.1 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
Authenticated command injection vulnerabilities exist in the web-based management interface of mobility conductors running AOS-8 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 · high confidence

Authenticated command injection vulnerabilities exist in the web-based management interface of Aruba Mobility Conductors running AOS-8. An authenticated attacker can inject arbitrary OS commands through the management interface, executing them with elevated (privileged) system privileges.

MitigationApply the vendor-released patch or firmware update for AOS-8 that addresses the command injection vulnerability. Restrict web management interface access to trusted networks and authorized personnel only.

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.6.0.0, < 8.10.0.21>= 8.11.0.0, < 8.13.1.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 device type
    Log into the device CLI and run 'show version' or 'show controller' to confirm this is an Aruba Mobility Conductor running AOS-8
    Affected if Device is not an Aruba Mobility Conductor running AOS-8 (not applicable)
  2. Check installed AOS version
    Execute 'show version' in the device CLI and note the displayed AOS version number
    Affected if Version cannot be determined or displayed
  3. Compare version to affected ranges
    Compare the installed version to: 8.6.0.0 through 8.10.0.20, or 8.11.0.0 through 8.13.1.0
    Affected if Installed version falls within >= 8.6.0.0 and < 8.10.0.21, OR >= 8.11.0.0 and < 8.13.1.1
  4. Verify web management interface status
    Check if the web-based management interface (WebUI) is enabled by running 'show web-server' or reviewing the management interface configuration
    Affected if Web management interface is enabled and accessible

Device is an Aruba Mobility Conductor running a vulnerable AOS-8 version (8.6.0.0-8.10.0.20 or 8.11.0.0-8.13.1.0) with the web management interface exposed.

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.21 / 8.13.1.1 or later
Fixed in 8.10.0.218.13.1.1
Interim mitigation

Apply the vendor-released patch or firmware update for AOS-8 that addresses the command injection vulnerability. Restrict web management interface access to trusted networks and authorized personnel only.

Recommended fix High confidence

ArubaOS 8.10.0.21 or later (for 8.6.x-8.10.x branches); ArubaOS 8.13.1.1 or later (for 8.11.x-8.13.x branches)

  1. 1. Identify the current ArubaOS version by checking the mobility conductor or controller.
  2. 2. Determine which version branch you are running (8.6.x - 8.10.x or 8.11.x - 8.13.x).
  3. 3. If running version 8.10.x or lower, upgrade to ArubaOS version 8.10.0.21 or later.
  4. 4. If running version 8.11.x or 8.12.x, upgrade to ArubaOS version 8.13.1.1 or later.
  5. 5. Verify the upgrade was successful and the vulnerability is remediated.
  6. 6. After upgrade, change credentials for all accounts that had access to the web management interface as a precautionary measure.
Caveat Review Aruba upgrade documentation for controller compatibility and ensure backup of configuration before upgrading

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

Fix this in Arubaos Scoped from the published advisory
  • Consultation4.0 h
  • Implementation4.0 h
  • Testing8.0 h
  • Review / QA4.0 h
20.0 hours of engineering $3,440
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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

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-37170 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