dbcve.org
ArubaosOperating system · Arubanetworks

CVE-2026-44863

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 multiple service components of Aruba AOS-8 and AOS-10 allow authenticated administrators to inject malicious input through the CLI and management protocol. This unsanitized input reaches backend database queries, enabling arbitrary OS command execution on the underlying system.

MitigationApply vendor security patches for AOS-8 and AOS-10; implement parameterized queries and proper input validation on all database-facing parameters; follow least-privilege principles for administrative accounts.

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 ArubaOS or SD-WAN version
    Access the device CLI and run 'show version' or 'show system information' to retrieve the exact firmware version. For management interface, check the dashboard or about page.
    Affected if 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, 8.13.0.0 to 8.13.1.1; AOS-10: 10.4.0.0 to 10.4.1.10, 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, 8.7.0.0-2.3.0.0 to 8.7.0.0-2.3.0.9
  2. Confirm the product is Aruba AOS-8, AOS-10, or SD-WAN
    From the version output, verify the product line is Arubanetworks Arubaos or Arubanetworks Sd Wan. This vulnerability does not affect other Aruba product lines.
    Affected if The product is ArubaOS-8, ArubaOS-10, or Aruba SD-WAN and the version is in the affected ranges above.
  3. Verify CLI and management protocol access is enabled
    Check configuration with 'show running-config | include cli' or review management interface settings. SQL injection vectors exist in both CLI and management protocol components.
    Affected if CLI access or the management protocol service is enabled, which is the default configuration for administrative access.
  4. Identify if the device has authenticated administrator accounts
    Review user database with 'show user-database' or check AAA configuration. The vulnerability requires an authenticated administrator session to inject malicious SQL input.
    Affected if Any local or remote administrator accounts exist and are usable for authentication to the device.

You are affected if the device runs ArubaOS-8, ArubaOS-10, or Aruba SD-WAN within the version ranges listed AND has administrator accounts configured for CLI or management interface access.

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 security patches for AOS-8 and AOS-10; implement parameterized queries and proper input validation on all database-facing parameters; follow least-privilege principles for administrative accounts.

Recommended fix High confidence

ArubaOS: 8.10.0.22+ (8.10.x), 8.12.0.7+ (8.12.x), 8.13.1.2+ (8.13.x), 10.4.1.11+ (10.4.x); SD-WAN: versions > 8.6.0.4-2.2.0.7 and > 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 which version branch your current installation falls into (6.5.x, 8.10.x, 8.11.x, 8.12.x, 8.13.x, 10.4.x for ArubaOS; or 8.6.x, 8.7.x for SD-WAN)
  3. 3. For ArubaOS: If running 6.5.4.0 through 8.10.x, upgrade to 8.10.0.22 or later (preferably latest 8.10.x stable)
  4. 4. For ArubaOS: If running 8.11.x, upgrade to 8.12.0.7 or later
  5. 5. For ArubaOS: If running 8.13.0.0 through 8.13.1.1, upgrade to 8.13.1.2 or later
  6. 6. For ArubaOS: If running 10.4.0.0 through 10.4.1.10, upgrade to 10.4.1.11 or later
  7. 7. For SD-WAN: If running 8.6.0.4-2.2.0.x, upgrade to the next available patch beyond 8.6.0.4-2.2.0.7
  8. 8. For SD-WAN: If running 8.7.0.0-2.3.0.x, upgrade to the next available patch beyond 8.7.0.0-2.3.0.9
Caveat Upgrades may require downtime and should be tested in a staging environment first; some legacy configurations may need review after major version jumps

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
  • Testing12.0 h
  • Review / QA6.0 h
42.0 hours of engineering $7,360
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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