CVE-2026-23814
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 parameters of a certain AOS-CX CLI command could allow a low-privilege authenticated remote attacker to inject malicious commands resulting in unwanted behavior.
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 exists in the AOS-CX CLI where malicious commands can be injected through command parameters by an authenticated low-privilege attacker, potentially leading to arbitrary command execution with elevated privileges.
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<= 10.10.1170>= 10.13.0000, <= 10.13.1160>= 10.16.0000, <= 10.16.1020>= 10.17.0000, <= 10.17.0001CVSS 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.
-
Confirm AOS-CX product in useIdentify if the network device runs ArubaOS-CX by checking the system banner, firmware version, or device model information via 'show version' or 'show system' CLI commandsAffected if Device is confirmed to be running ArubaOS-CX firmware
-
Determine installed AOS-CX versionExecute 'show version' in the CLI and note the firmware version string (for example: 'Version 8.x.x.x' or similar)Affected if Installed version falls within the vulnerable version range (compare to known affected versions for this CVE)
-
Verify CLI interface accessibilityConfirm that CLI access is enabled and reachable via console, SSH, or telnet by checking management settings with 'show management-cli-status' or similar management configuration commandsAffected if CLI interface is accessible from network or console
-
Review user account privilege levelsList all local user accounts and their privilege roles using 'show user' or 'show aaa local-user' commands to identify any low-privilege accountsAffected if Low-privilege authenticated users exist who can access the CLI
-
Inspect for anomalous command execution logsReview command history or audit logs (if available via 'show audit-logs' or external syslog) for unexpected or suspicious command patterns, especially commands containing shell operators (;, |, &&, ||, $())
A user is affected if their ArubaOS-CX device runs a vulnerable firmware version AND has CLI access enabled for low-privilege authenticated users.
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 dataApply vendor-provided patches for ArubaOS-CX when available. Until then, limit CLI access to trusted personnel only, enforce least-privilege principles for user accounts, and monitor for anomalous command patterns.
- Consultation3.0 h
- Implementation6.0 h
- Testing3.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 $3,984.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-23814 — 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-23814 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