CVE-2026-23820
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 · uneditedA vulnerability in the command line interface of Access Points running AOS-10 and AOS-8 Instant could allow an authenticated remote attacker to execute system commands in a restricted shell environment. Successful exploitation could allow an 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 confidenceA command injection vulnerability in the CLI of Aruba Access Points running AOS-10 and AOS-8 Instant allows authenticated attackers to escape the restricted shell environment and execute arbitrary operating system commands.
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.4.0.0, <= 6.5.4.24>= 8.4.0.0, < 8.10.0.22>= 8.11.0.0, < 8.12.0.7>= 8.13.0.0, < 8.13.1.2>= 10.3.0.0, < 10.4.1.11>= 10.5.0.0, < 10.7.2.3= 10.8.0.0CVSS 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 checksWork through these to decide whether this CVE applies to you.
-
Identify Aruba Access Point modelLog into the Aruba AP CLI or web interface and run 'show version' or check the device inventory to confirm the hardware model is an Aruba Access PointAffected if Device is an Aruba Access Point running AOS-10 or AOS-8 Instant firmware
-
Check AOS firmware versionRun 'show version' in the Aruba AP CLI or check the web interface firmware status. Look for version strings indicating AOS-10.x or AOS-8 InstantAffected if Firmware version is AOS-10 or AOS-8 Instant (any version within these product lines)
-
Verify CLI management is enabledCheck the AP configuration via 'show running-config' or the web interface under Management > CLI settings to confirm CLI access is permittedAffected if CLI management interface is enabled and accessible to authenticated users
-
Confirm authentication methodsReview local user accounts and RADIUS/TACACS+ configurations via 'show users' or 'show aaa authentication' commandsAffected if Any user account (local or remote) can authenticate to the CLI, allowing escape of the restricted shell
If you have Aruba Access Points running AOS-10 or AOS-8 Instant with CLI access enabled for any authenticated user, your environment is potentially affected by this command injection vulnerability.
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.
From vendor data8.10.0.228.12.0.78.13.1.2
Apply vendor-supplied firmware updates from Aruba for affected AOS-10 and AOS-8 Instant versions; enforce least-privilege access to CLI management and monitor for unauthorized command execution.
- Consultation8.0 h
- Implementation20.0 h
- Testing12.0 h
- Review / QA4.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $12,352.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-23820 — 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-23820 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