ArubaosOperating system · Arubanetworks

CVE-2026-44853

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 could allow an authenticated remote attacker to upload arbitrary files to the underlying operating system, potentially leading to remote code execution as a privileged user.

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 in the web-based management interface of Aruba AOS-8 and AOS-10 allow authenticated attackers to upload arbitrary files to the underlying operating system. This file upload capability can be leveraged to achieve remote code execution with privileged (root) user privileges.

MitigationApply vendor-provided patches or firmware updates for AOS-8 and AOS-10. Restrict access to the web-based management interface to trusted IP addresses only and enforce strong authentication credentials.

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 AOS version
    Access the device CLI and run 'show version' or 'show inventory' to display the firmware version. For SD-WAN devices, use 'show version' or check the web interface version info.
    Affected if The displayed version falls within any of the affected ranges: AOS-8 versions 6.5.4.0 through 8.10.0.21, 8.11.0.0 through 8.12.0.6, or 8.13.0.0 through 8.13.1.1; AOS-10 versions 10.4.0.0 through 10.4.1.10 or 10.5.0.0 through 10.7.2.2; SD-WAN versions 8.6.0.4-2.2.0.0 through 8.6.0.4-2.2.0.7 or 8.7.0.
  2. Confirm web-based management interface is accessible
    Check if the device has the web-based management interface (WebUI) enabled by examining the HTTP/HTTPS service configuration. In CLI, run 'show web-server' or 'show http server' to display the web service status.
    Affected if The WebUI service is enabled and reachable, exposing the file upload functionality that contains the command injection vulnerability.
  3. Verify remote authentication configuration
    Check if the device allows remote authentication for web management by reviewing the management access settings. Use 'show authentication' or 'show aaa authentication' to see configured authentication methods.
    Affected if Remote authentication is configured for the web interface, allowing authenticated attackers to access the vulnerable file upload feature.
  4. Check management interface exposure
    Review which IP addresses or networks can reach the web management interface. Use 'show ip access-list' or check the management VLAN configuration to identify permitted management traffic sources.
    Affected if The web management interface is exposed to untrusted networks, increasing the likelihood of exploitation by remote authenticated attackers.

You are affected if your device runs an Aruba AOS-8 or AOS-10 version within the affected 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 patches or firmware updates for AOS-8 and AOS-10. Restrict access to the web-based management interface to trusted IP addresses only and enforce strong authentication credentials.

Recommended fix Moderate confidence

ArubaOS: 8.10.0.22, 8.12.0.7, 8.13.1.2, or 10.4.1.11 (depending on branch); SD-WAN: versions greater than 8.6.0.4-2.2.0.7 or 8.7.0.0-2.3.0.9

  1. 1. Identify the currently running ArubaOS or SD-WAN version by checking the device management interface or running 'show version'
  2. 2. Determine which version branch your current release belongs to (6.5.x, 8.10.x, 8.11.x, 8.12.x, 8.13.x, or 10.4.x for ArubaOS; 8.6.x or 8.7.x for SD-WAN)
  3. 3. For ArubaOS 8.10.x branch: upgrade to version 8.10.0.22 or later
  4. 4. For ArubaOS 8.11.x branch: upgrade to version 8.12.0.7 or later
  5. 5. For ArubaOS 8.13.x branch: upgrade to version 8.13.1.2 or later
  6. 6. For ArubaOS 10.4.x branch: upgrade to version 10.4.1.11 or later
  7. 7. For SD-WAN 8.6.x branch: upgrade to a version greater than 8.6.0.4-2.2.0.7
  8. 8. For SD-WAN 8.7.x branch: upgrade to a version greater than 8.7.0.0-2.3.0.9
Caveat Review HPE Aruba release notes for any known compatibility issues or configuration changes required when upgrading between major version branches

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

Fix this in Arubaos Scoped from the published advisory
  • Consultation6.0 h
  • Implementation12.0 h
  • Testing6.0 h
  • Review / QA4.0 h
28.0 hours of engineering $4,980
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,968.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-44853 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

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