dbcve.org
ArubaosOperating system · Arubanetworks

CVE-2025-37173

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
An improper input handling vulnerability exists in the web-based management interface of mobility conductors running either AOS-10 or AOS-8 operating systems. Successful exploitation could allow an authenticated malicious actor with valid credentials to trigger unintended behavior on the affected 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

An improper input handling vulnerability exists in the web-based management interface of Aruba mobility conductors running AOS-10 or AOS-8. An authenticated attacker with valid credentials can exploit improper input validation to trigger unintended behavior on the affected system.

MitigationApply vendor-supplied patches when available; in the interim, restrict web management interface access to trusted IP ranges and enforce strong credential policies to reduce the attack surface.

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:>= 6.5.4.0, < 8.10.0.21>= 8.11.0.0, < 8.13.1.1>= 10.3.0.0, < 10.4.1.10>= 10.5.0.0, < 10.7.2.2

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. Verify the web management interface is accessible
    Confirm that the Aruba device's web-based management interface (HTTPS/HTTP) is reachable from your network. This is typically on ports 443 or 8080. Check firewall rules and interface bindings.
    Affected if The web management interface is exposed and accessible from untrusted networks (the vulnerability requires an authenticated attacker to access this interface).
  2. Identify the installed ArubaOS version
    Access the device via CLI or web interface and retrieve the firmware/OS version. In CLI, this is commonly done with 'show version' or 'show system info'. Note the full version number including all three version fields (e.g., 8.10.0.15).
    Affected if The version falls within any of these ranges: 6.5.4.0 through 8.10.0.20, 8.11.0.0 through 8.13.1.0, 10.3.0.0 through 10.4.1.9, or 10.5.0.0 through 10.7.2.1.
  3. Confirm the device is a mobility conductor
    Verify the device role in the Aruba deployment. This can be checked via CLI commands like 'show controller' or 'show mobility-conductor' or via the web interface under Device > Controller. Mobility conductors centralize management in Aruba deployments.
    Affected if The device functions as a mobility conductor (the CVE specifically targets mobility conductors, though other Aruba devices running the affected versions may also be impacted).
  4. Review authentication settings for the web interface
    Check if weak or default credentials exist for web management accounts. Verify that strong password policies are enforced and that accounts are limited to trusted users only.
    Affected if The vulnerability requires a valid authenticated user to exploit; weak credentials or excess privileged accounts increase the realistic attack surface.

You are affected if your Aruba mobility conductor runs a web-accessible AOS version within 6.5.4.0-8.10.0.20, 8.11.0.0-8.13.1.0, 10.3.0.0-10.4.1.9, or 10.5.0.0-10.7.2.1 and the management interface is accessible to potential attackers.

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 / 10.4.1.10 or later
Fixed in 8.10.0.218.13.1.110.4.1.10
Interim mitigation

Apply vendor-supplied patches when available; in the interim, restrict web management interface access to trusted IP ranges and enforce strong credential policies to reduce the attack surface.

Recommended fix High confidence

Upgrade to ArubaOS 8.10.0.21+ (8.10.x), 8.13.1.1+ (8.11.x/8.12.x), 10.4.1.10+ (10.3.x), or 10.7.2.2+ (10.5.x/10.6.x) depending on your current branch

  1. 1. Identify the currently running ArubaOS version via the web interface (show version in CLI)
  2. 2. Determine which version branch you're on (8.10.x, 8.11.x/8.12.x, 10.3.x, or 10.5.x/10.6.x)
  3. 3. Download the appropriate fixed firmware version from support.hpe.com: for 8.10.x use >=8.10.0.21, for 8.11.x/8.12.x use >=8.13.1.1, for 10.3.x use >=10.4.1.10, for 10.5.x/10.6.x use >=10.7.2.2
  4. 4. Backup the current configuration via WebUI (Maintenance > Backup) or CLI (backup config)
  5. 5. Upload the new firmware image via WebUI (Maintenance > Firmware > Upload) or TFTP/FTP to the controller
  6. 6. Install the firmware and reboot the mobility conductor
  7. 7. After reboot, verify the new version is running and confirm all managed devices are online
  8. 8. Test critical functionality to ensure normal operation
Caveat Major version upgrades (e.g., 8.x to 10.x) may require configuration migration; review Aruba upgrade guide for your path

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
  • Testing10.0 h
  • Review / QA6.0 h
34.0 hours of engineering $5,940
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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