dbcve.org
ArubaosOperating system · Arubanetworks

CVE-2026-44852

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
An authenticated remote code execution vulnerability exists in the AOS-8 and AOS-10 web-based management interface. A vulnerability in the certificate download functionality could allow an authenticated remote attacker to overwrite arbitrary files on the underlying operating system by exploiting improper input validation in the file path parameter. Successful exploitation could allow the attacker to execute arbitrary commands on the underlying operating system 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

An authenticated remote code execution vulnerability in the AOS-8 and AOS-10 web management interface allows attackers to overwrite arbitrary files via the certificate download feature due to improper input validation in the file path parameter, enabling privileged command execution.

MitigationImplement strict input validation and path sanitization on the certificate download functionality to prevent path traversal, and restrict file write permissions for the web service account.

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 ArubaOS version
    Access the controller CLI and run 'show version' or check the web management interface footer for the version number
    Affected if The installed version falls within any of these 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 SD-WAN version
    Access the SD-WAN CLI or web interface and check the firmware or software version information
    Affected if The installed version is between 8.6.0.4-2.2.0.0 and 8.6.0.4-2.2.0.7 inclusive, or between 8.7.0.0-2.3.0.0 and 8.7.0.0-2.3.0.9 inclusive
  3. Verify web management interface accessibility
    Confirm whether the Aruba web management interface (HTTPS on port 4343 or 443) is exposed to network access
    Affected if The web management interface is accessible from untrusted networks and the device version is in the affected ranges
  4. Inspect certificate download feature logs
    Review web management interface logs or audit logs for requests to the certificate download endpoint with unusual path parameters
    Affected if Log entries show certificate download requests containing path traversal sequences like '../' or attempts to write to unexpected file locations
  5. Check for unauthorized file modifications
    Inspect the controller file system for newly created or modified executable files in web-accessible directories or system binary locations
    Affected if Unexpected files exist in web directories or system paths that were not deployed through official upgrade processes

A user is affected if their ArubaOS or SD-WAN device runs a version within the specified vulnerable ranges AND the web management interface is accessible, allowing an authenticated attacker to exploit the certificate download feature via path traversal.

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 strict input validation and path sanitization on the certificate download functionality to prevent path traversal, and restrict file write permissions for the web service account.

Recommended fix High confidence

ArubaOS 8.10.0.22+ / 8.12.0.7+ / 8.13.1.2+ / 10.4.1.11+; SD-WAN beyond 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 via the web UI (System > General > About) or CLI (show version)
  2. 2. Determine the appropriate upgrade path based on current version - upgrades must land on or beyond: ArubaOS 8.10.0.22, 8.12.0.7, 8.13.1.2, or 10.4.1.11; SD-WAN versions beyond 8.6.0.4-2.2.0.7 or 8.7.0.0-2.3.0.9
  3. 3. Download the appropriate firmware from the Aruba support portal (support.hpe.com) - ensure the file matches your hardware platform
  4. 4. Back up the current configuration via CLI (backup flash) or web UI before upgrading
  5. 5. Upload the new firmware image via web UI (Maintenance > Firmware > Upload) or SCP/FTP to the controller
  6. 6. Schedule a maintenance window as upgrades cause brief controller restarts
  7. 7. Initiate the upgrade via web UI (Maintenance > Firmware > Upgrade) or CLI (upgrade-software)
  8. 8. Verify the upgrade completed successfully and the new version is running (show version)
Caveat Major version jumps (e.g., 8.x to 10.x) may require configuration migration review; SD-WAN upgrades may have new CLI syntax

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

Fix this in Arubaos Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing4.0 h
  • Review / QA2.0 h
18.0 hours of engineering $3,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 $5,120.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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