dbcve.org
ArubaosOperating system · Arubanetworks

CVE-2026-44866

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 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

Command injection vulnerabilities exist in the web-based management interface of Aruba AOS-8 and AOS-10 operating systems. An authenticated attacker can inject arbitrary OS commands through unsanitized input fields in the management UI, achieving remote code execution on the underlying system.

MitigationApply vendor-provided security patches for AOS-8 and AOS-10. Restrict management interface access to trusted networks and implement network segmentation as defense-in-depth.

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. Determine the installed ArubaOS version
    Access the device CLI and run 'show version' to retrieve the current firmware version
    Affected if The version falls within any of these ranges: >= 6.5.4.0 and < 8.10.0.22, >= 8.11.0.0 and < 8.12.0.7, >= 8.13.0.0 and < 8.13.1.2, >= 10.4.0.0 and < 10.4.1.11, or >= 10.5.0.0 and < 10.7.2.3
  2. Determine the installed SD-WAN version
    Access the device CLI and run 'show version' or 'show sd-wan version' to retrieve the current firmware version
    Affected if The version falls within: >= 8.6.0.4-2.2.0.0 and <= 8.6.0.4-2.2.0.7, or >= 8.7.0.0-2.3.0.0 and <= 8.7.0.0-2.3.0.9
  3. Verify if the web-based management interface is enabled
    Run 'show web-server' or 'show web-management' in the CLI to check the status of the web interface
    Affected if The web-based management interface is enabled and accessible over the network
  4. Check if remote management access is permitted
    Run 'show ip http server' or 'show management interface' to verify web management is bound to accessible network interfaces
    Affected if Web management is bound to any interface other than localhost or is accessible from non-trusted networks
  5. Confirm authentication is required for the management interface
    Verify that the web interface requires valid credentials by attempting access or reviewing 'show user' and authentication configuration
    Affected if The management interface permits authenticated access, which is the normal condition for this vulnerability to be exploitable

Your environment is affected if you are running any ArubaOS version within the listed ranges (or SD-WAN versions within the listed ranges) and the web-based management interface is enabled and accessible.

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-provided security patches for AOS-8 and AOS-10. Restrict management interface access to trusted networks and implement network segmentation as defense-in-depth.

Recommended fix High confidence

ArubaOS: upgrade to 8.10.0.22+ (8.10.x branch), 8.12.0.7+ (8.11.x branch), 8.13.1.2+ (8.13.x branch), or 10.4.1.11+ (10.4.x branch) | SD-WAN: upgrade to 8.6.0.4-2.2.0.8+ or 8.7.0.0-2.3.1.0+

  1. 1. Identify the currently running ArubaOS or SD-WAN version from the device dashboard or via 'show version' command
  2. 2. Determine which version branch your current installation belongs to (6.5.x, 8.10.x, 8.11.x, 8.13.x, 10.4.x for ArubaOS or 8.6.x, 8.7.x for SD-WAN)
  3. 3. Download the appropriate fixed version from support.hpe.com based on your hardware model and current branch
  4. 4. Upload the new firmware to the Aruba device via WebUI (System > Platforms > Upgrade) or CLI ('upgrade-software')
  5. 5. Reboot the device to apply the new firmware
  6. 6. After reboot, verify the new version is installed and the web-based management interface is accessible
  7. 7. Confirm the vulnerability is resolved by validating the fixed version matches the minimum required version for your branch
Caveat Major version upgrades (e.g., 8.x to 10.x) may require configuration changes or controller migration; always review release notes for breaking changes before upgrading

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

Fix this in Arubaos Scoped from the published advisory
  • Consultation4.0 h
  • Implementation12.0 h
  • Testing8.0 h
  • Review / QA3.0 h
27.0 hours of engineering $4,700
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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