Skip to main content
Mallory
CriticalPublic exploitVulnerability

CVE-2026-23813: Authentication Bypass in Aruba AOS-CX Web Management Interface

Published Mar 11, 2026 · Updated 2 months ago
Trending this weekNot trendingOutside this week’s top 100
Mention activity · 30 daysNo mention activity in the last 30 days.
CVSS9.8Critical · v3.1
EPSS0.95%62nd percentile
CISA KEVNoNot listed
In the wildNonePublic exploit, no exploitation reported
Vendor
Hewlett Packard Enterprise
IdentifiersCVE-2026-23813CWE-288

CVE-2026-23813 is a critical authentication bypass vulnerability in the web-based management interface of HPE Aruba Networking AOS-CX switches. The flaw allows a remote, unauthenticated attacker to circumvent existing authentication controls exposed by the management interface. In some cases, successful exploitation can also trigger an administrator password reset, enabling takeover of the device management plane. Reported affected release trains include AOS-CX 10.17.0001 and earlier, 10.16.1020 and earlier, 10.13.1160 and earlier, and 10.10.1170 and earlier. The vulnerability is network-reachable, requires no prior authentication or user interaction, and has been described with a CVSS v3.1 vector of AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H.

Do you run this?See affected versions in your environment and whether adversaries are exploiting this vulnerability against assets like yours.
Check your exposure
Analyst brief

Impact, mitigation & remediation

What it means and what to do now: patch path, interim mitigations, and the assume-compromise checklist.

Impact

What an attacker gets, and what they’ve been doing with it.

Successful exploitation allows an unauthenticated remote actor to bypass authentication protecting the AOS-CX web management interface. In affected cases, the attacker may reset the administrator password and obtain full administrative control of the switch. This can result in compromise of confidentiality, integrity, and availability of the device, including unauthorized configuration changes, security control bypass, disruption of switching operations, and broader control of the network infrastructure managed by the affected system.

Mitigation

If you can’t patch tonight, do this now.

If immediate patching is not possible, restrict access to management interfaces to trusted administrative sources only and isolate the management plane on a dedicated Layer 2 segment or VLAN with strict Layer 3 access controls. Disable HTTP(S) management on switched virtual interfaces and routed ports where it is not required. Protect REST and HTTP management services with control-plane ACLs that permit only authorized clients. Enable detailed accounting, logging, and continuous monitoring to detect unauthorized access attempts or suspicious management activity.

Remediation

Patch, then assume compromise.

Upgrade affected Aruba AOS-CX systems to vendor-fixed releases. Reported fixed versions include AOS-CX 10.17.1001 or later, 10.16.1030 or later, 10.13.1161 or later, and 10.10.1180 or later. Apply the relevant HPE Aruba Networking security updates across all affected release trains and validate that the web management interface is running a remediated build after deployment.

Public exploits

Exploits

1 exploit validated by Mallory's analysis. Hidden: 1 rejected by Mallory's analysis as not a working exploit.

View more in app →
CVE-2026-23813Repository contains a small Python proof-of-concept suite for CVE-2026-23813, an authentication bypass in HPE Aruba Networking AOS-CX caused by an overly permissive nginx regex for public login endpoints. Structure is straightforward: three Python scripts (`detect.py`, `bypass_demo.py`, `exploit.py`) plus defensive/detection documentation and patch/root-cause notes. `detect.py` is a non-destructive scanner that sends a single GET to `/rest/v1/system/users/loginpoc` and classifies the target as PATCHED if nginx returns 401, otherwise VULNERABLE because the request reached the backend. `bypass_demo.py` compares a normal request to `/rest/v1/system/users/admin` with a smuggled request to `/rest/v1/system/users/loginpoc` to illustrate the bypass mechanics. `exploit.py` is the main exploit: it requires a checkpoint name containing `login`, then POSTs to `/rest/v1/config/copy/running-config/<name>` to create a checkpoint and GETs `/rest/v1/fullconfigs/<name>` to retrieve the full running configuration, printing user password hashes. The exploit is network/web based, targets the HTTPS management API, and is operational rather than weaponized because it includes a working hardcoded exploitation chain but not a flexible framework. The repository also includes `detection/suricata.rules` and `detection/nginx-access.md` for identifying exploit attempts, and `docs/root-cause.md` / `docs/patch-diff.md` explaining that vulnerable nginx used `^/rest/(|v.*/)login`, allowing slash-containing version segments and trailing `login*` tokens to bypass authentication before proxying the raw URI to the backend.offseckit · Disclosed May 23, 2026 · python · markdown · network · webOperational
Exposure surface

Affected products & vendors

Products and vendors Mallory has correlated with this vulnerability. Open in Mallory to drill down to specific CPE configurations and version ranges.

VendorProductType
Hewlett Packard EnterpriseArubaos-Cxoperating_system
FAQ

Frequently asked questions

Is CVE-2026-23813 exploited in the wild?
As of Sep 25, 2026, Mallory has no reports of CVE-2026-23813 being exploited in the wild. It is not listed in CISA KEV.
Is there a public exploit for CVE-2026-23813?
Yes. Mallory tracks 1 public exploit or proof of concept for CVE-2026-23813, the earliest disclosed May 23, 2026.
Is there a patch for CVE-2026-23813?
Upgrade affected Aruba AOS-CX systems to vendor-fixed releases. Reported fixed versions include AOS-CX 10.17.1001 or later, 10.16.1030 or later, 10.13.1161 or later, and 10.10.1180 or later.
What products are affected by CVE-2026-23813?
Hewlett Packard Enterprise Arubaos-Cx.
How severe is CVE-2026-23813?
CVE-2026-23813 has a CVSS v3.1 score of 9.8 (Critical) and an EPSS score of 0.95% (62nd percentile) as of Sep 25, 2026.
Activity feed

Recent activity

14 sources tracked across advisories, community write-ups, and news. New activity surfaces here as Mallory finds it.

View more in app →
+2 more in the timeline. Sign up to see them
Do you run this?See affected versions in your environment and whether adversaries are exploiting this vulnerability against assets like yours.
Check your exposure
Mallory platform

The version that knows your environment.

This page is what’s public. Mallory adds the parts that aren’t: which of your assets are affected, which adversaries are exploiting it right now, and which detections to deploy tonight.
Exposure mappingQuery your assets running an affected version, and investigate the blast radius.
Threat actor evidenceEvery report linking this CVE to a named adversary.
Associated malwareMalware families linked to this CVE, with evidence and IOCs.
Detection signaturesYARA, Sigma, Snort, and vendor rules, auto-deployed to your SIEM.
Vendor-by-vendor mappingCross-references every affected SKU, including bundled OEM variants.
Social activity8Community discussion across Reddit, Mastodon, and other social sources.