Live Exposure Defense: From CVE to Confirmed Exposure in 12 Hours – See more

Back
New CVE Detected

CVE-2026-73777 – Authentication Bypass / Privilege Escalation – Aruba AOS-CX (10.10.x–10.18.x)

Be the first to know when new zero-days emerge:

Subscribe to Email Alerts
Subscribe to RSS Feed

Summary

CVE-2026-73777 is an authorization bypass vulnerability in the API endpoint of HPE Aruba Networking AOS-CX switches that could allow an unauthenticated remote actor to circumvent existing authentication controls. It affects multiple AOS-CX release trains and carries a CVSS v3.1 base score of 8.1 (High). The flaw was disclosed as part of HPE Security Bulletin HPESBNW05134, published September 1, 2026, alongside a broader set of AOS-CX vulnerabilities.

Technical details

  • Root cause: an authorization bypass in an AOS-CX API endpoint that fails to properly enforce authentication controls.
  • Trigger conditions: HPE describes the attack complexity as high, and no privileges or user interaction are required to exploit the flaw.
  • Attack vector: network-based, exploitable remotely against the exposed API endpoint.
  • Impact: successful exploitation can circumvent authentication controls, with HPE rating full impact to confidentiality, integrity, and availability of the switch.

Affected software

  • HPE Aruba Networking AOS-CX 10.18.0000 through 10.18.0001
  • HPE Aruba Networking AOS-CX 10.17.0000 through 10.17.1021
  • HPE Aruba Networking AOS-CX 10.16.0000 through 10.16.1051
  • HPE Aruba Networking AOS-CX 10.13.0000 through 10.13.1180
  • HPE Aruba Networking AOS-CX 10.10.0000 through 10.10.1180 (End of Maintenance branch)

Severity

  • CVSS v3.1 Base Score: 8.1 (High)
  • Vector: CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H

Mitigation and recommended actions

  • Immediate: Upgrade to the fixed releases identified in HPESBNW05134 — AOS-CX 10.18.1002 and above, 10.17.1030 and above, 10.16.1060 and above, 10.13.1190 and above, or 10.10.1181 and above — obtained via the HPE Networking Support Portal.
  • If patching is not immediately possible: restrict the CLI and web-based management interfaces to a dedicated Layer 2 segment/VLAN, and/or control access with Layer 3+ firewall policies, along with accounting controls to track and log user activity, as recommended in the HPE advisory.

How IONIX identifies potentially affected assets

IONIX matches the following signals against data already collected when it crawled the asset; identifying the technology sends no request beyond that crawl.

  • (Signal details from the IONIX AOS-CX fingerprint plugin were not provided for this CVE, so no in-scope passive signals are listed here.)

References

Are you exposed?

Get a free report of your organization’s exposure to this CVE and threat

  • Mapping of all Assets with this Technology
  • Identification of potentially exposed assets to this CVE
  • Confirmation of verified exploitable assets
Get Exposure Report

How IONIX’s External Exposure Management Platform Detects and Validates
Zero-Days to Shrink MTTR

1

Map your entire attack surface (continously)

IONIX uses multi-factor discovery methods, including DNS analysis, certificate mapping, metadata inspection, and more, to automatically map every internet-facing asset across your environment. This includes cloud instances, third-party platforms, shadow IT, and even forgotten infrastructure that traditional tools miss.

2

Monitor for new CVEs

Dozens of threat intel feeds using agentic technology are continuously analyzed to detect the appearance of proof-of-concept code, exploit kits, and indicators of active targeting. IONIX goes further by applying AI to proactively evaluate whether emerging vulnerabilities are likely to be exploited, even before PoCs go public.

3

Identify Potential External Exposures

Not all CVEs matter. IONIX filters vulnerabilities by asking attacker-centric questions: Can it be reached from the internet? Does it require authentication? Is it being exploited in the wild? This dramatically reduces noise and focuses teams on threats that can actually be weaponized.

4

Create Safe, Scalable Exploit Validations

IONIX transforms real-world PoCs into safe, non-intrusive test payloads that can be run in production environments without disruption. These simulations are precisely targeted to the systems that are vulnerable, ensuring rapid validation without unnecessary load.

5

Execute Exploit Validations

By combining context about software stack, versioning, exposure status, and reachability, IONIX ensures that only the right payloads are executed against the right assets, maximizing efficiency and minimizing risk.

6

Drive Fast and Actionable Remediation

Results are routed through integrations with ticketing, SOAR, and SIEM tools. Issues are written in plain language, bundled into remediation clusters, and prioritized based on asset criticality, exploitability, and blast radius. This shortens mean time to remediation (MTTR) and empowers teams to act with confidence.

Are you exposed?

Get a free report of your organization’s exposure to this CVE and threat

  • Mapping of all Assets with this Technology
  • Identification of potentially exposed assets to this CVE
  • Confirmation of verified exploitable assets
Get Exposure Report
Close

Subscribe to Threat Center RSS

Copy/paste the link below into your preferred RSS reader or follow these instructions to subscribe to Slack alerts.

Open RSS feedSlack setup instructions

Close

Get Real-Time CVE Alerts to Your Email

Be the first to know when new zero-days emerge