dbcve.org
ArubaosOperating system · Arubanetworks

CVE-2026-44870

HIGH · 8.8 CVSS v3.1 Published 2026-05-12
Fix available
A fix is available. Upgrade to 8.10.0.22 / 8.12.0.7 or later.
See remediation →
94/100
Remediation priority · Urgent
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
Command injection vulnerabilities exist in the command line interface (CLI) service accessed by the PAPI protocol of AOS-8 and AOS-10 Operating Systems. Successful exploitation of these vulnerabilities could allow an authenticated remote attacker to 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

Command injection vulnerabilities exist in the CLI service accessed via the PAPI protocol in Aruba AOS-8 and AOS-10 operating systems. An authenticated remote attacker can exploit these vulnerabilities to execute arbitrary commands on the underlying operating system, potentially gaining full system compromise.

MitigationApply vendor-supplied patches for AOS-8 and AOS-10 when available. Restrict PAPI protocol access to trusted management networks and authenticated administrators only.

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.22>= 8.11.0.0, < 8.12.0.7>= 8.13.0.0, < 8.13.1.2>= 10.4.0.0, < 10.4.1.11>= 10.5.0.0, < 10.7.2.3
Sd WanApplication
Affected:>= 8.6.0.4-2.2.0.0, <= 8.6.0.4-2.2.0.7>= 8.7.0.0-2.3.0.0, <= 8.7.0.0-2.3.0.9

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
Low
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:L/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 ArubaOS or SD-WAN version
    Run 'show version' or 'show controller version' from the CLI to retrieve the installed software version
    Affected if The version falls within any of these ranges: AOS-8: >= 6.5.4.0 to < 8.10.0.22, >= 8.11.0.0 to < 8.12.0.7, >= 8.13.0.0 to < 8.13.1.2; AOS-10: >= 10.4.0.0 to < 10.4.1.11, >= 10.5.0.0 to < 10.7.2.3; SD-WAN: >= 8.6.0.4-2.2.0.0 to <= 8.6.0.4-2.2.0.7 or >= 8.7.0.0-2.3.0.0 to <= 8.7.0.0-2.3.0.9
  2. Verify PAPI protocol is enabled
    Run 'show papi status' or check the PAPI configuration in the management profile settings to see if the PAPI protocol handler is active
    Affected if PAPI protocol is enabled and accessible on the device
  3. Confirm management access to PAPI
    Review management interface configurations using 'show ip management' or 'show interface mgmt' to determine which IP addresses or networks can reach the PAPI service (port 8211)
    Affected if PAPI is reachable from untrusted networks or the management interface is exposed to non-management networks
  4. Check CLI authentication configuration
    Run 'show user-database' or review 'aaa authentication CLI' settings to see which users have CLI access and confirm if unnecessary admin accounts exist
    Affected if Multiple administrative users have CLI access or authentication is not restricted to essential personnel only

You are affected if your device runs an ArubaOS or SD-WAN version within the affected ranges AND the PAPI protocol is accessible from your management network with authenticated CLI users present.

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.22 / 8.12.0.7 / 8.13.1.2 or later
Fixed in 8.10.0.228.12.0.78.13.1.2
Interim mitigation

Apply vendor-supplied patches for AOS-8 and AOS-10 when available. Restrict PAPI protocol access to trusted management networks and authenticated administrators only.

Recommended fix High confidence

ArubaOS: 8.10.0.22+ (for 8.10.x), 8.12.0.7+ (for 8.11.x-8.12.x), 8.13.1.2+ (for 8.13.x), 10.4.1.11+ (for 10.4.x); SD-WAN: 8.6.0.4-2.2.0.8+ or 8.7.0.0-2.3.0.10+

  1. 1. Identify the currently installed ArubaOS or SD-WAN version by running 'show version' in the CLI
  2. 2. Determine the appropriate upgrade path based on your current major version (8.x, 10.x, or SD-WAN)
  3. 3. Download the corresponding fixed release from support.hpe.com
  4. 4. Upload the firmware to the Aruba device using 'copy tftp://<server>/<file> flash:' or via the WebUI
  5. 5. Verify the image integrity using 'verify image' command
  6. 6. Schedule a maintenance window as upgrades require device reboot
  7. 7. Install the firmware using 'boot system' command
  8. 8. After reboot, confirm the new version with 'show version' and verify the vulnerability is resolved
Caveat Review HPE Aruba release notes for any configuration changes or deprecated features between your current version and the target fixed version; test in a 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
  • Consultation6.0 h
  • Implementation8.0 h
  • Testing4.0 h
  • Review / QA2.0 h
20.0 hours of engineering $3,600
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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