dbcve.org
ArubaosOperating system · Arubanetworks

CVE-2025-37138

MEDIUM · 6.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 →
64/100
Remediation priority · Elevated
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 authenticated command injection vulnerability exists in the command line interface binary of AOS-10 GW and AOS-8 Controllers/Mobility Conductor operating system. Exploitation of this vulnerability requires physical access to the hardware controllers. A successful attack could allow an authenticated malicious actor with physical access 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 vulnerability in the CLI binary of AOS-10 GW and AOS-8 Controllers/Mobility Conductor allows an authenticated malicious actor with physical access to execute arbitrary commands as a privileged user on the underlying operating system.

MitigationApply available vendor patches for ArubaOS 10.x and 8.x. Restrict physical access to hardware controllers and enforce strict access controls for CLI 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
Physical
Complexity
Low
Privileges
High
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:P/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. Check ArubaOS version
    Execute 'show version' or 'show system info' on the controller CLI to retrieve the installed ArubaOS version number
    Affected if The 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 device model is affected
    Execute 'show controller-info' or check the hardware model to verify the device is an AOS-10 GW or AOS-8 Controller/Mobility Conductor
    Affected if The device is an AOS-10 gateway or AOS-8 controller/conductor model
  3. Verify CLI access is enabled
    Check if the CLI service is active by attempting to access the console, SSH, or telnet interface on the device
    Affected if CLI access (console, SSH, or telnet) is available and authentication is configured
  4. Assess physical access controls
    Inspect physical security controls around the controller hardware - verify who has console access and whether unauthorized physical access is possible
    Affected if Physical access to the device console or CLI interface is not restricted to trusted personnel only

A defender is affected if the device runs a vulnerable ArubaOS version (within the ranges above), is an AOS-10 GW or AOS-8 Controller/Conductor, has CLI access enabled, and physical access to the CLI interface is possible by an authenticated actor.

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 available vendor patches for ArubaOS 10.x and 8.x. Restrict physical access to hardware controllers and enforce strict access controls for CLI 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 respective versions)

  1. Identify the currently installed ArubaOS version using 'show version' command
  2. Determine which version branch is in use (8.10.x, 8.12.x, 8.13.x, or 10.4.x)
  3. Download the appropriate fixed version from HPE Aruba support portal: 8.10.0.19 or later for 8.10.x branch, 8.12.0.6 or later for 8.12.x branch, 8.13.1.0 or later for 8.13.x branch, or 10.4.1.9 or later for 10.4.x branch
  4. Upload the firmware to the controller/conductor using 'upgrade-software' or WebUI
  5. Reboot the device to apply the new firmware
  6. Verify the version has been updated using 'show version' command
  7. Ensure physical access controls are in place as this vulnerability requires physical access

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

Fix this in Arubaos Scoped from the published advisory
  • Consultation4.0 h
  • Implementation2.0 h
  • Testing4.0 h
  • Review / QA2.0 h
12.0 hours of engineering $2,120
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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