Unauthenticated path traversal in AOS-8 networking OS enables file read/modify/delete on appliances; impacts widely deployed Aruba/HPE network infrastructure and can cause device compromise.
CVE-2026-79866
Unauthenticated path traversal in AOS-8 PAPI allows OS file access and device compromise.
Is CVE-2026-79866 being exploited?
Not confirmed. CVE-2026-79866 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-79866?
CVE-2026-79866 is rated Critical with a CVSS score of 9.6. 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-79866?
Not known from our data. No patch reference has been recorded for CVE-2026-79866, 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-79866 affect?
CVE-2026-79866 affects AOS-8 (PAPI protocol), Aruba/HPE networking appliances running AOS-8. Confirm the exact affected versions against the vendor advisory before deciding you are exposed.
What should I do about CVE-2026-79866?
Isolate/block PAPI access, restrict adjacency, monitor devices, apply vendor updates when released.
Exploitation status reflects CISA's KEV catalog as we last synced it. Check the catalog directly.
Unauthenticated adjacent attacker can read, modify, and delete OS files on AOS-8 devices, potentially leading to device takeover and persistent compromise.
Immediate action required
- affected>= 8.13.0.0 and <= 8.13.3.0
- affected>= 8.10.0.0 and <= 8.10.0.23
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.