Skip to content
major vulnerability· requires attention

iLO is widely deployed across enterprise servers; an auth bypass enables remote admin control of server management, risking broad infrastructure disruption and full server compromise.

Infrastructure

CVE-2026-79820

9.0
Critical
EPSS n/aPatch availableOct 6, 2026

Remote authentication bypass in HPE iLO 7 allowing administrative takeover of server management

common questions

Is CVE-2026-79820 being exploited?

Not confirmed. CVE-2026-79820 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.

How severe is CVE-2026-79820?

CVE-2026-79820 is rated Critical with a CVSS score of 9.0. 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-79820?

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

What does CVE-2026-79820 affect?

CVE-2026-79820 affects HPE Integrated Lights-Out (iLO) 7 firmware, HPE ProLiant servers with iLO7. Confirm the exact affected versions against the vendor advisory before deciding you are exposed.

What should I do about CVE-2026-79820?

Apply HPE iLO7 firmware updates immediately and restrict/segment iLO network access

Exploitation status reflects CISA's KEV catalog as we last synced it. Check the catalog directly.

executive summary
technical analysis
affected
HPE Integrated Lights-Out (iLO) 7 firmwareHPE ProLiant servers with iLO7
impact

Authentication bypass grants remote administrative iLO access (power, KVM, firmware updates), enabling full server compromise or disruption.

action required

Immediate action required

affected versions
Hewlett Packard Enterprise (HPE) HPE Integrated Lights-Out (iLO) 7
  • affected1.25.00

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