dbcve.org
ArubaosOperating system · Arubanetworks

CVE-2025-37132

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 arbitrary file write vulnerability exists in the web-based management interface of both the AOS-10 GW and AOS-8 Controller/Mobility Conductor operating systems. Successful exploitation could allow an authenticated malicious actor to upload arbitrary files and execute arbitrary commands 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 arbitrary file write vulnerability in AOS-10 GW and AOS-8 Controller/Mobility Conductor web management interface allows uploading files that can lead to OS command execution.

MitigationRestrict web management interface access to trusted IP addresses/networks, audit and limit administrative accounts, and apply vendor patches when available.

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 device and OS version
    Access the device CLI and run 'show version' or 'show controller-info' to identify the device model (AOS-10 GW or AOS-8 Controller/Mobility Conductor) and installed ArubaOS version
    Affected if The device is an Aruba AOS-10 GW or AOS-8 Controller/Mobility Conductor running a version that falls within: 8.10.0.0-8.10.0.18, 8.12.0.0-8.12.0.5, 8.13.0.0-8.13.0.x, 10.4.0.0-10.4.1.8, or 10.7.0.0-10.7.2.0
  2. Confirm the web management interface is enabled
    Run 'show web-server' in the CLI to check if the web management interface (WebUI) is enabled and note the listening interface/address
    Affected if Web management interface is enabled and accessible from the network segment you are auditing
  3. Check for exposed web management access
    Review the 'ip http server' and 'ip https server' configuration via 'show running-config | include http' to determine if the web interface is bound to non-loopback addresses
    Affected if The HTTP/HTTPS web management is bound to a routable IP address rather than localhost/loopback only
  4. Verify administrative account presence
    Run 'show user-database' or 'show local-userdb' to enumerate administrative accounts that could authenticate to the web interface
    Affected if Any administrative accounts exist that could be used to authenticate to the vulnerable web upload functionality

You are affected if you have an Aruba AOS-10 GW or AOS-8 Controller/Mobility Conductor running any of the listed affected versions with the web management interface enabled and accessible from your network.

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 web management interface access to trusted IP addresses/networks, audit and limit administrative accounts, and apply vendor patches when available.

Recommended fix High confidence

Upgrade to ArubaOS 8.10.0.19+, 8.12.0.6+, 8.13.1.0+, or 10.4.1.9+ depending on your current branch

  1. 1. Identify the current ArubaOS version by navigating to the web-based management interface and checking the Dashboard or by running 'show version' in the CLI.
  2. 2. Determine which version branch you are currently running (8.10.x, 8.12.x, 8.13.x, or 10.4.x).
  3. 3. Download the appropriate fixed ArubaOS version from the HPE Aruba Support Portal at support.hpe.com. The fixed versions are: 8.10.0.19 or later for the 8.10 branch, 8.12.0.6 or later for the 8.12 branch, 8.13.1.0 or later for the 8.13 branch, and 10.4.1.9 or later for the 10.4 branch.
  4. 4. Create a full backup of the current configuration using 'backup flash' command or via the web interface under Maintenance > Backup & Restore.
  5. 5. Schedule a maintenance window as upgrades require device downtime.
  6. 6. Upload the new ArubaOS firmware file via the web interface (Maintenance > Software Management > Upload) or via CLI using 'copy tftp: <tftp-server> <file> flash:' command.
  7. 7. Reboot the device to apply the new firmware using 'reload' command or via the web interface.
  8. 8. After the device restarts, verify the new version is installed using 'show version' and confirm the fix is applied.
Caveat Major version upgrades between branches (e.g., 8.x to 10.x) may require configuration migration and feature compatibility review; always test in a lab environment first

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
  • Testing8.0 h
  • Review / QA4.0 h
30.0 hours of engineering $5,280
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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