Targets HPE Networking AOS-10, a widely deployed enterprise network OS; exploitation can disrupt network services and enable further access, posing broad operational risk.
CVE-2026-79883
Unauthenticated buffer overflow in HPE AOS-10 PAPI allows info disclosure and service disruption.
Is CVE-2026-79883 being exploited?
Not confirmed. CVE-2026-79883 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.22% probability of exploitation in the next 30 days.
How severe is CVE-2026-79883?
CVE-2026-79883 is rated High with a CVSS score of 8.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-79883?
Not known from our data. No patch reference has been recorded for CVE-2026-79883, 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-79883 affect?
CVE-2026-79883 affects HPE Networking AOS-10, PAPI protocol, HPE switches running AOS-10. Confirm the exact affected versions against the vendor advisory before deciding you are exposed.
What should I do about CVE-2026-79883?
Apply vendor updates/mitigations ASAP; block PAPI from untrusted networks and enforce management-plane ACLs.
Exploitation status reflects CISA's KEV catalog as we last synced it. Check the catalog directly.
Adjacent unauthenticated attacker can retrieve sensitive info and interrupt AOS-10 services; may enable lateral access to network resources.
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.