dbcve.org
ArubaosOperating system · Arubanetworks

CVE-2026-44865

HIGH · 7.2 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 →
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
Command injection vulnerabilities exist in the web-based management interface 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 · high confidence

CVE-2026-44865 is a command injection vulnerability in the web-based management interface of Aruba AOS-8 and AOS-10 operating systems. An authenticated remote attacker can exploit insufficient input validation in the management interface to inject and execute arbitrary operating system commands with the privileges of the web service. This grants the attacker full control over the underlying network device.

MitigationApply the vendor-supplied patches for AOS-8 and AOS-10 to remediate the command injection vulnerability. Until patches are available, restrict web management interface access to trusted admin networks only and monitor for indicators of compromise.

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
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 installed Aruba product and version
    Access the device CLI and run 'show version' or access the web management interface to view the software version information. For SD-WAN devices, check via the SD-WAN controller interface or CLI.
    Affected if The product is Aruba AOS-8, AOS-10, or SD-WAN and the version falls within any of these ranges: AOS-8: 6.5.4.0 to 8.10.0.21, 8.11.0.0 to 8.12.0.6, or 8.13.0.0 to 8.13.1.1; AOS-10: 10.4.0.0 to 10.4.1.10 or 10.5.0.0 to 10.7.2.2; 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. Verify if web-based management interface is enabled
    In the CLI, run 'show web-server' or check the WebUI configuration via the management interface settings. Confirm whether HTTPS or HTTP management access is active.
    Affected if Web-based management interface (WebUI) is enabled and accessible, as this is the attack surface for the command injection flaw.
  3. Confirm authentication method and user access
    Check for user accounts with access to the web management interface by reviewing 'show user' or 'show aaa authentication' in the CLI, and verify if external authentication (RADIUS/TACACS) or local accounts are in use.
    Affected if Any authenticated user with access to the web management interface can exploit this vulnerability, as it requires only valid credentials.

The environment is affected if the device runs any of the vulnerable AOS-8, AOS-10, or SD-WAN versions listed AND has the web-based management interface enabled with accessible user accounts.

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 the vendor-supplied patches for AOS-8 and AOS-10 to remediate the command injection vulnerability. Until patches are available, restrict web management interface access to trusted admin networks only and monitor for indicators of compromise.

Recommended fix Moderate confidence

ArubaOS: upgrade to 8.10.0.22+ (8.10 branch), 8.12.0.7+ (8.11/8.12 branch), 8.13.1.2+ (8.13 branch), or 10.4.1.11+ (10.4 branch). SD-WAN: upgrade to patched versions available from HPE Aruba support.

  1. 1. Identify the currently installed ArubaOS or SD-WAN version from the device CLI or web interface
  2. 2. Determine which version branch your current installation falls into (8.10.x, 8.11.x, 8.12.x, 8.13.x, 10.4.x for ArubaOS; 8.6.x or 8.7.x for SD-WAN)
  3. 3. Download the appropriate fixed version from support.hpe.com: ArubaOS 8.10.0.22+, 8.12.0.7+, 8.13.1.2+, or 10.4.1.11+; SD-WAN fixed versions per branch
  4. 4. Upload the firmware file through the web-based management interface or via CLI using the appropriate upgrade command
  5. 5. Verify the upgrade completes successfully and the device restarts with the fixed version
  6. 6. Confirm the vulnerability is remediated by checking the system shows the fixed ArubaOS/SD-WAN version
Caveat Standard Aruba upgrade procedures apply; review release notes for any configuration or compatibility changes between versions

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

Fix this in Arubaos Scoped from the published advisory
  • Consultation4.0 h
  • Implementation3.0 h
  • Testing6.0 h
  • Review / QA2.0 h
15.0 hours of engineering $2,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 $4,160.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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