dbcve.org
ArubaosOperating system · Arubanetworks

CVE-2026-44855

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
Stack-based buffer overflow vulnerabilities exist in several underlying management service components accessed through the command-line interface of the AOS-8 and AOS-10 Operating Systems. An authenticated attacker with administrative privileges could exploit these vulnerabilities by sending specially crafted requests to the affected services. Successful exploitation could allow the attacker to execute arbitrary code with elevated privileges 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

Stack-based buffer overflow vulnerabilities in management service components of Aruba OS-8 and OS-10 allow authenticated administrators to send specially crafted CLI requests that trigger the overflow, enabling arbitrary code execution with elevated privileges.

MitigationApply vendor-provided patches for AOS-8 and AOS-10 when available, limit administrative CLI access to trusted personnel only, and monitor for indicators of exploitation attempts.

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 installed ArubaOS version
    Execute `show version` or `show version extensive` from the CLI console
    Affected if The displayed version falls within any of the affected 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; >= 10.5.0.0 and < 10.7.2.3
  2. Identify installed SD-WAN version
    Execute `show version` on SD-WAN appliances or check the management interface for the firmware version
    Affected if The version is >= 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 management CLI service status
    Check if the CLI management service is enabled and accessible via `show management` or `show cli status`
    Affected if The management CLI service is active and reachable (the vulnerability requires authenticated administrator access to send malicious CLI requests)
  4. Review administrator accounts and access logs
    Use `show user-database` and review CLI access logs for any unauthorized or suspicious administrator sessions
    Affected if There are unexpected administrator accounts or login activity from unknown sources

You are affected if your ArubaOS or SD-WAN version falls within the affected version ranges AND the management CLI service is accessible to authenticated administrators.

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 for AOS-8 and AOS-10 when available, limit administrative CLI access to trusted personnel only, and monitor for indicators of exploitation attempts.

Recommended fix High confidence

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

  1. 1. Identify the currently installed ArubaOS or SD-WAN version by running 'show version' on the device CLI.
  2. 2. Determine the product family (ArubaOS or SD-WAN) and current major version branch from the affected versions list.
  3. 3. For ArubaOS: If running version 6.5.4.0 through 8.10.x, upgrade to 8.10.0.22 or later; if running 8.11.x, upgrade to 8.12.0.7 or later; if running 8.13.x, upgrade to 8.13.1.2 or later; if running 10.4.x, upgrade to 10.4.1.11 or later.
  4. 4. For SD-WAN: If running 8.6.0.4-2.2.0.x, upgrade to a version newer than 8.6.0.4-2.2.0.7; if running 8.7.0.0-2.3.0.x, upgrade to a version newer than 8.7.0.0-2.3.0.9.
  5. 5. Download the appropriate fixed firmware from the HPE Aruba support portal (support.hpe.com).
  6. 6. Review HPE Aruba upgrade documentation for any prerequisite steps such as controller reboots or configuration backups.
  7. 7. Upload the firmware to the device and initiate the upgrade following standard Aruba upgrade procedures.
  8. 8. After upgrade, verify the new version is installed by running 'show version' and confirm the vulnerability is resolved.
Caveat Review HPE Aruba release notes for potential compatibility issues or configuration changes required when upgrading across 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
  • Testing10.0 h
  • Review / QA4.0 h
32.0 hours of engineering $5,580
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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