CVE-2026-44871
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 · uneditedCommand injection vulnerabilities exist in the command line interface (CLI) service accessed by the PAPI protocol of AOS-8 and AOS-10 Operating Systems. Successful exploitation of these vulnerabilities could allow an authenticated remote 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 confidenceCommand injection vulnerabilities exist in the CLI service accessed via the PAPI protocol on Aruba AOS-8 and AOS-10 operating systems. An authenticated remote attacker can inject and execute arbitrary operating system commands by sending specially crafted requests through the PAPI interface.
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>= 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>= 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.9CVSS 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
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:L/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 checksWork through these to decide whether this CVE applies to you.
-
Identify the installed ArubaOS versionRun 'show version' or 'show system information' from the CLI console to retrieve the exact firmware versionAffected if The version falls within any of the affected 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) or AOS-10 (10.4.0.0 to 10.4.1.10, 10.5.0.0 to 10.7.2.2)
-
Identify the installed SD-WAN versionRun 'show version' on SD-WAN devices or check the management console for the firmware build numberAffected if The version is between 8.6.0.4-2.2.0.0 and 8.6.0.4-2.2.0.7, or between 8.7.0.0-2.3.0.0 and 8.7.0.0-2.3.0.9
-
Verify PAPI service statusRun 'show process papi' or check the process list for 'papi' daemon running on the controllerAffected if The PAPI process is running and listening on the management interface
-
Check PAPI network exposureReview access control lists and firewall rules for UDP port 8211 (PAPI default port). Use 'show ip access-list' and check management interface bindingsAffected if PAPI (port 8211/UDP) is accessible from untrusted networks or management interface is bound to non-loopback addresses without IP restrictions
-
Confirm PAPI authentication configurationRun 'show running-config | include papi' or check the PAPI section in the management configurationAffected if PAPI access is enabled for administrative accounts without additional IP-based access restrictions
You are affected if your Aruba device runs a version within the affected ranges AND the PAPI service is enabled and reachable from your network.
Generated from the published advisory. Verify against your own configuration.
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 · scoped8.10.0.228.12.0.78.13.1.2
Apply vendor-supplied patches for AOS-8 and AOS-10 when released. Until patches are available, restrict network access to the PAPI management interface to trusted administrative IPs only and review all accounts with PAPI access.
ArubaOS: 8.10.0.22+ / 8.12.0.7+ / 8.13.1.2+ / 10.4.1.11+ ; SD-WAN: 8.6.0.4-2.2.0.8+ / 8.7.0.0-2.3.1.0+
- 1. Identify the currently installed ArubaOS or SD-WAN version by running 'show version' or checking the device management interface.
- 2. For ArubaOS 8.10.x deployments: upgrade to version 8.10.0.22 or later.
- 3. For ArubaOS 8.11.x deployments: upgrade to version 8.12.0.7 or later (may require passing through 8.12.0.0).
- 4. For ArubaOS 8.13.x deployments: upgrade to version 8.13.1.2 or later.
- 5. For ArubaOS 10.4.x deployments: upgrade to version 10.4.1.11 or later.
- 6. For SD-WAN 8.6.0.4-2.2.0.x deployments: upgrade to version 8.6.0.4-2.2.0.8 or later.
- 7. For SD-WAN 8.7.0.0-2.3.0.x deployments: upgrade to version 8.7.0.0-2.3.1.0 or later.
- 8. Verify the upgrade was successful by confirming the new version with 'show version'.
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation4.0 h
- Implementation8.0 h
- Testing6.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $5,600.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-44871 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2026-44871 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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