dbcve.org
ArubaosOperating system · Arubanetworks

CVE-2025-37135

MEDIUM · 6.5 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 →
71/100
Remediation priority · Elevated
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
Arbitrary file deletion vulnerabilities have been identified in the command-line interface of an AOS-8 Controller/Mobility Conductor. Successful exploitation of these vulnerabilities could allow an authenticated remote malicious actor to delete arbitrary files within 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

Arbitrary file deletion vulnerability in the CLI of Aruba AOS-8 Controller/Mobility Conductor allows an authenticated remote attacker to delete arbitrary files on the filesystem. The vulnerability stems from insufficient input validation or improper path handling in CLI command processing, enabling path traversal or unrestricted file deletion capabilities.

MitigationApply vendor-provided patches for AOS-8 Controller/Mobility Conductor. Restrict CLI access to trusted administrators only and implement network segmentation to limit exposure of management interfaces.

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
None
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:N/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 ArubaOS version
    Access the controller CLI and run 'show version' or access the WebUI to view the system firmware version
    Affected if The displayed version falls within any of these ranges: 8.10.0.0-8.10.0.18, 8.12.0.0-8.12.0.5, 8.13.0.0-8.13.0.x (before 8.13.1.0), 10.4.0.0-10.4.1.8, or 10.7.0.0-10.7.2.0
  2. Confirm the specific version number
    Run 'show version detailed' or check the WebUI System > General page for the exact build number
    Affected if The full version string shows a build before the patched releases (8.10.0.19, 8.12.0.6, 10.4.1.9, or 10.7.2.1)
  3. Determine if CLI management is enabled and accessible
    Verify CLI access is available via console, SSH, or telnet by attempting to connect or checking 'show management' output
    Affected if CLI access is enabled and the device is reachable over the network
  4. Review CLI command logging for suspicious file deletion activity
    Check CLI audit logs or run 'show audit' to look for unusual file deletion commands or path traversal patterns in recent sessions

You are affected if your ArubaOS version is one of the listed versions and your CLI is accessible to untrusted users, since the vulnerability allows authenticated attackers to delete arbitrary files through the CLI interface.

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

Apply vendor-provided patches for AOS-8 Controller/Mobility Conductor. Restrict CLI access to trusted administrators only and implement network segmentation to limit exposure of management interfaces.

Recommended fix High confidence

ArubaOS 8.10.0.19, 8.12.0.6, 8.13.1.0, or 10.4.1.9 (or later stable releases within each respective branch)

  1. 1. Identify the current ArubaOS version by running 'show version' in the CLI
  2. 2. Determine the appropriate upgrade path based on current version (8.10.x, 8.12.x, 8.13.x, or 10.4.x)
  3. 3. Download the corresponding fixed ArubaOS image from support.hpe.com (Aruba Support Portal)
  4. 4. Back up the current configuration using 'backup flash' or 'write mem' commands
  5. 5. Upload the new ArubaOS image to the controller via 'copy tftp://<server>/<image> flash:' or via WebUI
  6. 6. Verify the image integrity using 'verify image' command
  7. 7. Reboot the system using 'reload' command
  8. 8. After reboot, confirm the new version is running with 'show version'
Caveat Standard upgrade precautions apply - ensure configuration compatibility and test in non-production environment first

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

Fix this in Arubaos Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing6.0 h
  • Review / QA4.0 h
22.0 hours of engineering $3,860
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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