Affects HPE Aruba AOS-10 network OS used across enterprises; allows admin takeover and config changes that can disrupt corporate networks.
CVE-2026-79873
Authentication bypass in AOS-10 PAPI allowing administrative takeover.
Is CVE-2026-79873 being exploited?
Not confirmed. CVE-2026-79873 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.24% probability of exploitation in the next 30 days.
How severe is CVE-2026-79873?
CVE-2026-79873 is rated Critical with a CVSS score of 9.3. 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-79873?
Not known from our data. No patch reference has been recorded for CVE-2026-79873, which is not the same as no patch existing — a fix may have shipped without a tagged reference, or after this record was written. The vendor advisory is the only authority on whether a fix exists, and mitigations may be available regardless.
What does CVE-2026-79873 affect?
CVE-2026-79873 affects HPE Aruba AOS-10, Access points and controllers running AOS-10, Network infrastructure devices using AOS-10. Confirm the exact affected versions against the vendor advisory before deciding you are exposed.
What should I do about CVE-2026-79873?
Isolate management plane, restrict adjacent access, apply vendor patch ASAP when released.
Exploitation status reflects CISA's KEV catalog as we last synced it. Check the catalog directly.
Adjacent unauthenticated attacker can bypass PAPI auth to gain admin access, modify configurations, and access or manipulate sensitive data.
Immediate action required
- affected>= 10.8.0.0 and <= 10.8.1.1
- affected>= 10.7.0.0 and <= 10.7.2.6
- affected>= 10.4.0.0 and <= 10.4.1.13
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.