RCE in a widely deployed enterprise network OS (AOS-10) enabling privileged code execution on infrastructure devices; likely high-impact across organizations.
CVE-2026-79879
Memory corruption in AOS-10 allows privileged remote code execution.
Is CVE-2026-79879 being exploited?
Not confirmed. CVE-2026-79879 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.36% probability of exploitation in the next 30 days.
How severe is CVE-2026-79879?
CVE-2026-79879 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-79879?
Not known from our data. No patch reference has been recorded for CVE-2026-79879, 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-79879 affect?
CVE-2026-79879 affects AOS-10 (HPE/Aruba network OS), Network controllers/switches/access points running AOS-10. Confirm the exact affected versions against the vendor advisory before deciding you are exposed.
What should I do about CVE-2026-79879?
Follow HPE advisory: apply vendor patches/mitigations, isolate affected devices, restrict adjacent network access.
Exploitation status reflects CISA's KEV catalog as we last synced it. Check the catalog directly.
Unauthenticated adjacent attacker can trigger memory corruption to run arbitrary privileged code on the device OS.
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.