dbcve.org
ArubaosOperating system · Arubanetworks

CVE-2025-37171

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 · moderate confidence

Authenticated command injection vulnerabilities exist in the web-based management interface of Aruba mobility conductors running AOS-8. An authenticated attacker can execute arbitrary commands as a privileged user on the underlying operating system through the management interface.

MitigationApply available vendor patches for AOS-8, restrict management interface access to trusted networks, and enforce strong authentication for administrative accounts.

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. Confirm device is an Aruba mobility conductor running AOS-8
    Access the device console or CLI and run the command to display system information (for example, 'show version' or 'show system info'). Identify if the device is an Aruba mobility conductor and note the operating system version.
    Affected if The device is not an Aruba mobility conductor or is not running AOS-8.
  2. Determine the installed AOS-8 version
    From the system information output, locate the exact AOS version number (for example, 8.6.x.x, 8.10.x.x, 8.11.x.x, or 8.13.x.x). Compare this version against the affected ranges: 8.6.0.0 through 8.10.0.20, or 8.11.0.0 through 8.13.1.0.
    Affected if The installed version falls within >= 8.6.0.0 and < 8.10.0.21, or >= 8.11.0.0 and < 8.13.1.1.
  3. Verify the web-based management interface is enabled
    Check the device configuration for the web-based management interface status. This is typically found in the management settings or HTTP/HTTPS server configuration (for example, 'show management' or check the WebUI service configuration).
    Affected if The web-based management interface is enabled and accessible from the network segment being tested.
  4. Confirm authentication to the management interface is possible
    Attempt to log in to the web-based management interface with valid administrative credentials, or verify that valid administrative accounts exist in the device user database.
    Affected if An authenticated attacker can access the management interface with administrative privileges.

The environment is affected if the device is an Aruba mobility conductor running AOS-8 with a version in the vulnerable ranges AND the web-based management interface is accessible to an authenticated attacker.

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 available vendor patches for AOS-8, restrict management interface access to trusted networks, and enforce strong authentication for administrative accounts.

Recommended fix High confidence

ArubaOS 8.10.0.21 or later in 8.10.x branch; or ArubaOS 8.13.1.1 or later in 8.13.x branch (8.13.x is recommended for latest fixes)

  1. 1. Back up the current ArubaOS configuration via the web interface or CLI (backup configuration)
  2. 2. Download the fixed ArubaOS version (8.10.0.21 or later, or 8.13.1.1 or later) from support.hpe.com
  3. 3. Log in to the Mobility Conductor web-based management interface
  4. 4. Navigate to Maintenance > Software > Upload Software and upload the fixed ArubaOS image
  5. 5. Navigate to Maintenance > Software > Upgrade Software and select the uploaded image to install
  6. 6. After upgrade completes, verify the system is operational and confirm the new version under Maintenance > Software > Software Management
  7. 7. Verify normal controller functionality and critical services are running
Caveat Ensure compatibility with your existing APs and check the Aruba release notes for any behavioral changes between your current version and the target upgrade version

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

Fix this in Arubaos Scoped from the published advisory
  • Consultation6.0 h
  • Implementation12.0 h
  • Testing6.0 h
  • Review / QA4.0 h
28.0 hours of engineering $4,980
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2025-37171 — 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-37171 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