dbcve.org
ArubaosOperating system · Arubanetworks

CVE-2026-44860

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
SQL injection vulnerabilities exist in several underlying service components accessible through the AOS-8 and AOS-10 command-line interface and management protocol. An authenticated attacker with administrative privileges could exploit these vulnerabilities by injecting crafted input into parameters that are passed unsanitized to backend database queries. Successful exploitation could allow the 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

SQL injection vulnerabilities in AOS-8 and AOS-10 CLI and management protocol components allow authenticated attackers with administrative privileges to inject malicious input into parameters that are passed unsanitized to backend database queries, potentially achieving arbitrary OS command execution.

MitigationApply vendor patches or upgrades to patched versions of AOS-8 and AOS-10; restrict administrative access to trusted personnel 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 installed ArubaOS version
    Run 'show version' command in CLI or check the management interface for the firmware version
    Affected if Version falls within 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
    Run 'show version' or check the SD-WAN controller interface for the software version
    Affected if Version falls within ranges: >= 8.6.0.4-2.2.0.0 and <= 8.6.0.4-2.2.0.7; >= 8.7.0.0-2.3.0.0 and <= 8.7.0.0-2.3.0.9
  3. Confirm administrative CLI access is enabled
    Check if CLI management access is configured with 'show ip ssh' or review management access policies in the controller
    Affected if Administrative CLI or management protocol access is exposed to users who could inject SQL payloads
  4. Review audit logs for suspicious SQL-like patterns
    Examine logs using 'show log all' or management interface logs for unusual query patterns, especially in CLI command history
    Affected if Logs contain unexpected SQL syntax, UNION SELECT statements, or database function calls in user inputs

Your environment is affected if the installed ArubaOS or SD-WAN version matches any of the affected ranges AND administrative CLI or management access is available to authenticated users.

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 patches or upgrades to patched versions of AOS-8 and AOS-10; restrict administrative access to trusted personnel only and monitor for indicators of compromise.

Recommended fix High confidence

ArubaOS: 8.10.0.22 (for 6.5.x-8.9.x), 8.12.0.7 (for 8.11.x), 8.13.1.2 (for 8.13.x), 10.4.1.11 (for 10.4.x) | SD-WAN: versions greater than 8.6.0.4-2.2.0.7 and 8.7.0.0-2.3.0.9

  1. 1. Identify the current ArubaOS or SD-WAN version running on the affected device using 'show version' command
  2. 2. Determine the appropriate upgrade path based on current version: for ArubaOS 6.5.4.0-8.9.x upgrade to 8.10.0.22 or later; for 8.11.x upgrade to 8.12.0.7 or later; for 8.13.x upgrade to 8.13.1.2 or later; for 10.4.x upgrade to 10.4.1.11 or later
  3. 3. For SD-WAN: if running 8.6.0.4-2.2.0.x upgrade to version after 8.6.0.4-2.2.0.7; if running 8.7.0.0-2.3.0.x upgrade to version after 8.7.0.0-2.3.0.9
  4. 4. Download the appropriate fixed version from HPE Aruba support portal (support.hpe.com) using valid support entitlements
  5. 5. Review Aruba upgrade documentation for pre-upgrade checks and version-specific migration requirements
  6. 6. Backup current configuration before performing upgrade
  7. 7. Upload and install the fixed version following Aruba's standard upgrade procedure
  8. 8. Verify the upgrade was successful and confirm the device is running the fixed version
Caveat Upgrade may require downtime; review Aruba upgrade guide for version-specific migration steps and ensure configuration compatibility with target version

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

Fix this in Arubaos Scoped from the published advisory
  • Consultation8.0 h
  • Implementation16.0 h
  • Testing8.0 h
  • Review / QA4.0 h
36.0 hours of engineering $6,400
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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