Skip to content
Networks

CVE-2026-73777

8.1
High
EPSS 0.27%Patch availableSep 2, 2026

Unauthenticated API authentication bypass in HPE Aruba AOS-CX switches.

common questions

Is CVE-2026-73777 being exploited?

Not confirmed. CVE-2026-73777 does not appear in CISA's Known Exploited Vulnerabilities catalog, which records only exploitation that has been observed and reported publicly. That is evidence of absence of a report, not evidence the flaw is unattacked. EPSS currently estimates a 0.27% probability of exploitation in the next 30 days.

How severe is CVE-2026-73777?

CVE-2026-73777 is rated High with a CVSS score of 8.1. Severity describes how bad exploitation would be, not how likely it is: pair it with exploitation evidence before deciding what to patch first.

Is there a patch for CVE-2026-73777?

Yes. A fix has been recorded for CVE-2026-73777. The vendor advisory is the authority on the exact fixed version — apply it from there rather than from a summary.

What does CVE-2026-73777 affect?

CVE-2026-73777 affects HPE Aruba AOS-CX switches, AOS-CX API endpoints. Confirm the exact affected versions against the vendor advisory before deciding you are exposed.

What should I do about CVE-2026-73777?

Install vendor patch ASAP; restrict API access via ACLs/firewall.

Exploitation status reflects CISA's KEV catalog as we last synced it. Check the catalog directly.

executive summary
technical analysis
affected
HPE Aruba AOS-CX switchesAOS-CX API endpoints
impact

Remote unauthenticated actor can bypass API auth to access/modify switch configs, exfiltrate data, or maintain persistent access.

action required

Immediate action required

affected versions
Hewlett Packard Enterprise (HPE) AOS-CX
  • affected>= 10.18.0000 and <= 10.18.0001
  • affected>= 10.17.0000 and <= 10.17.1021
  • affected>= 10.16.0000 and <= 10.16.1051
  • affected>= 10.13.0000 and <= 10.13.1180
  • affected>= 10.10.0000 and <= 10.10.1180

As published in the CVE Program record. A version outside these ranges is not a statement that it is unaffected — vendors sometimes understate a range, and distribution-backported builds carry upstream numbers that do not reflect what was patched into them.

how to fix
Remediation steps are tailored for users whose stack is affected. Add this technology to your stack to see the fix checklist.
references
get alerted

Track only the vulnerabilities that affect your infrastructure.

start for free