dbcve.org
Arubaos CxOperating system · Hpe

CVE-2026-23817

MEDIUM · 6.1 CVSS v3.1 Published 2026-03-11
Fix available
A fix is available. Upgrade to 10.10.1180 / 10.13.1161 or later.
See remediation →
68/100
Remediation priority · Elevated
Remotely reachable No privileges

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 vulnerability in the web-based management interface of AOS-CX Switches could allow an unauthenticated remote attacker to redirect users to an arbitrary URL.

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 confidence

An open redirect vulnerability exists in the web-based management interface of Aruba OS-CX switches. An unauthenticated remote attacker can craft malicious URLs that redirect users to arbitrary websites, potentially leading to phishing attacks or credential theft.

MitigationRestrict access to the switch management interface to trusted networks only (e.g., via firewall rules or VPN). If possible, disable external access to the web management interface or apply available vendor patches.

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
Arubaos CxOperating system
Affected:>= 10.06.0000, < 10.10.1180>= 10.13.0000, < 10.13.1161>= 10.16.0000, < 10.16.1030>= 10.17.0000, < 10.17.1001

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
None
User interaction
Required
Scope
Changed
Confidentiality
Low
Integrity
Low
Availability
None

CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/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. Determine the installed Aruba OS-CX version
    Access the switch CLI and run the command 'show version' to display the current OS-CX firmware version.
    Affected if The version output falls within any of these ranges: 10.06.0000 to 10.10.1179, 10.13.0000 to 10.13.1160, 10.16.0000 to 10.16.1029, or 10.17.0000 to 10.17.1000.
  2. Verify the web-based management interface is enabled
    Run 'show web-management' in the CLI to confirm the web management service is currently active on the switch.
    Affected if The web management interface is enabled (status shows as 'enabled' or 'active').
  3. Check network access scope for the management interface
    Review the current configuration with 'show running-config' and look for web management ACLs or management interface bindings. Also check if the management interface (typically interface 0/0) is bound to VLANs accessible from untrusted networks.
    Affected if The web management interface is reachable from networks outside your trusted administrative zone (for example, from user VLANs or the internet-facing interface).

You are affected if the switch runs a version within the affected ranges AND the web-based management interface is enabled and accessible from untrusted networks.

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 10.10.1180 / 10.13.1161 / 10.16.1030 or later
Fixed in 10.10.118010.13.116110.16.1030
Interim mitigation

Restrict access to the switch management interface to trusted networks only (e.g., via firewall rules or VPN). If possible, disable external access to the web management interface or apply available vendor patches.

Recommended fix High confidence

10.10.1180 (for 10.6.x branch), 10.13.1161 (for 10.13.x branch), 10.16.1030 (for 10.16.x branch), or 10.17.1001 (for 10.17.x branch) - or migrate to the latest stable 10.17.x release

  1. Identify the current AOS-CX version by running 'show version' on the switch CLI
  2. Determine which version branch you are currently running (10.6.x, 10.13.x, 10.16.x, or 10.17.x)
  3. Schedule a maintenance window and back up the current configuration using 'write memory' and/or 'backup config'
  4. Download the appropriate fixed firmware version from the HPE/Aruba Support portal (support.hpe.com) - select the minimum fixed version for your branch: 10.10.1180 for 10.6.x, 10.13.1161 for 10.13.x, 10.16.1030 for 10.16.x, or 10.17.1001 for 10.17.x
  5. Transfer the firmware file to the switch using TFTP, USB, or SCP
  6. Initiate the firmware upgrade using 'firmware upload <filename.tar>' followed by 'reload' or via the Web UI under Maintenance > Firmware
  7. After the switch reboots, verify the new version is installed with 'show version'
  8. Confirm the upgrade was successful and test that the web interface no longer permits arbitrary URL redirection
Caveat Standard AOS-CX firmware upgrades typically preserve configuration; however, always verify compatibility with existing modules and review release notes for any known issues or migration considerations

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

Fix this in Arubaos Cx Scoped from the published advisory
  • Consultation4.0 h
  • Implementation4.0 h
  • Testing4.0 h
  • Review / QA2.0 h
14.0 hours of engineering $2,480
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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