Skip to content
major vulnerability· requires attention

Affects HPE AOS-CX, a widely deployed network OS; unauthenticated RCE could lead to device and wide network compromise, causing major operational disruption.

Networks

CVE-2026-73752

8.8
High
EPSS 0.32%Patch availableSep 2, 2026

Unauthenticated API file-write in HPE AOS-CX enabling potential RCE.

common questions

Is CVE-2026-73752 being exploited?

Not confirmed. CVE-2026-73752 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.32% probability of exploitation in the next 30 days.

How severe is CVE-2026-73752?

CVE-2026-73752 is rated High with a CVSS score of 8.8. 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-73752?

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

What does CVE-2026-73752 affect?

CVE-2026-73752 affects HPE Aruba AOS-CX (network OS), Managed switches running AOS-CX. Confirm the exact affected versions against the vendor advisory before deciding you are exposed.

What should I do about CVE-2026-73752?

Apply vendor patch immediately; restrict API access and isolate affected devices.

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 (network OS)Managed switches running AOS-CX
impact

Unauthenticated attacker can write arbitrary files to the OS via an API, enabling remote code execution, persistence, and full device/network compromise.

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