dbcve.org
ArubaosOperating system · Arubanetworks

CVE-2026-44873

MEDIUM · 5.4 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 →
60/100
Remediation priority · Elevated
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
A session management vulnerability in AOS-8 allows previously authenticated users to retain network access after their accounts are administratively disabled. Existing sessions are not invalidated when credentials are revoked, enabling continued access until session expiration. An attacker with compromised credentials could exploit this behavior to maintain unauthorized access even after the account has been disabled.

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

AOS-8 fails to invalidate active sessions when administrator-disable user accounts. When credentials are revoked or accounts are disabled, existing authenticated sessions remain valid until natural expiration, allowing continued network access.

MitigationImplement proper session invalidation logic that checks account status on each request and terminates sessions immediately upon account disable/revocation.

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
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
Low
Integrity
Low
Availability
None

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:L/A:N

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. Check ArubaOS version
    Run 'show version' on the Aruba controller CLI or check via WebUI under Maintenance > Controller > Controller Versions
    Affected if The version displayed is >= 6.5.4.0 and < 8.10.0.22, OR >= 8.11.0.0 and < 8.12.0.7, OR >= 8.13.0.0 and < 8.13.1.2
  2. Check SD-WAN version
    Run 'show version' on the SD-WAN device or check via WebUI under Dashboard > System > Version
    Affected if The version displayed 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. Identify disabled user accounts
    Run 'show user-table' or 'show aaa authentication-user' to list local users, then cross-reference with 'show aaa authentication-user <username>' for each user to identify accounts with status 'disabled' or 'disabled' flag set
    Affected if Any local administrator accounts exist with disabled status in the system
  4. Check for active sessions from disabled accounts
    Run 'show user-table' or 'show sessions' to list currently active authenticated sessions, then compare usernames against the list of disabled accounts from step 3
    Affected if Active sessions exist in the output that correspond to usernames of disabled accounts, indicating those sessions were not invalidated upon account disable

You are affected if your device runs an ArubaOS or SD-WAN version within the affected ranges AND active sessions still exist for accounts that have been disabled, because those sessions should have been terminated but remain valid until natural expiration.

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

Implement proper session invalidation logic that checks account status on each request and terminates sessions immediately upon account disable/revocation.

Recommended fix High confidence

ArubaOS: 8.10.0.22 or later for 8.10.x branch; 8.12.0.7 or later for 8.11.x/8.12.x branch; 8.13.1.2 or later for 8.13.x branch | SD-WAN: 8.6.0.4-2.2.0.8 or later; 8.7.0.0-2.3.1.0 or later

  1. 1. Identify the current ArubaOS or SD-WAN version by checking the device dashboard or running 'show version'
  2. 2. Determine which upgrade path applies based on your current version branch (6.5.4.x->8.10.x, 8.11.x->8.12.x, or 8.13.x->8.13.1.x)
  3. 3. Download the appropriate fixed version from HPE Aruba support portal (support.hpe.com)
  4. 4. Schedule a maintenance window as upgrades require device restart
  5. 5. Backup current configuration using 'backup flash' or via the WebUI
  6. 6. Upload the firmware file to the device via WebUI or SCP
  7. 7. Perform the upgrade using 'upgrade-software' CLI command or via WebUI
  8. 8. After upgrade, verify the new version is installed with 'show version'
Caveat Standard ArubaOS upgrade precautions apply: review release notes for known issues, test in non-production environment first, and ensure adequate controller redundancy for clustered deployments

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

Fix this in Arubaos Scoped from the published advisory
  • Consultation3.0 h
  • Implementation12.0 h
  • Testing6.0 h
  • Review / QA3.0 h
24.0 hours of engineering $4,200
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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