Skip to main content

HPE iLO 7 CVE-2026-79820

| EUVDEUVD-2026-92433 CRITICAL
Improper Authentication (CWE-287)
2026-10-05 hpe GHSA-8q8h-2xfx-27cp
9.0
CVSS 3.1 · Vendor: hpe
View

Attack ChainAIDerived

Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain

  1. Access
    Reach iLO 7 management interface
  2. Delivery
    Send crafted validation request
  3. Exploit
    Bypass user authentication check
  4. Execution
    Gain administrative BMC session
  5. Impact
    Control or disrupt managed host

Vulnerability Assessment

Weakness
CWE
OWASP Top 10:2025
A07:2025 - Authentication Failures
ASVS 5.0
V6 - Authentication Authentication mechanism validation
MITRE ATT&CK

2 techniques across 2 tactics: Defense Evasion, Initial Access

The technique list with ATT&CK links and the kill-chain view is part of the Basic plan and up.

Exploitation Conditions

Exploitation requires network reachability to the HPE iLO 7 management interface (typically a dedicated out-of-band management LAN), and no authentication or user interaction is needed (PR:N/UI:N). The key limiting factor is high attack complexity (AC:H): the 'remote user validation failure' is condition-dependent, so a successful bypass likely hinges on specific preconditions, state, or timing rather than a single deterministic request. Real-world risk is further bounded where iLO interfaces are segmented onto isolated management networks and not exposed to general or internet-facing access. Exact vulnerable firmware builds are not specified in the provided data and should be confirmed against the HPE bulletin.

Impact

This is a genuinely high-priority flaw, not a CVSS-inflated paper tiger, because the affected component is a baseboard management controller (BMC). The CVSS 9.0 is driven by unauthenticated network reachability (AV:N/PR:N/UI:N), full CIA impact (C:H/I:H/A:H), and a scope change (S:C) - consistent with an iLO authentication/validation bypass that would grant out-of-band control over the host server. The one meaningful brake is AC:H (high attack complexity), which indicates the 'user validation failure' is not trivially triggerable and likely depends on specific conditions, timing, or a non-deterministic state the attacker must win - this is what separates it from a straightforward remote auth bypass. Exploitation signals are otherwise thin: no CISA KEV listing and no public exploit identified at time of analysis, so there is currently no evidence of active exploitation or weaponization. EPSS is not provided in the input and cannot be cited. SSVC inputs (exploitation, automatable, technical impact) were not supplied; technical impact is clearly 'total' given C:H/I:H/A:H, but 'automatable' is uncertain and arguably 'no' given AC:H. Conflict to verify: the input Tags label this 'Information Disclosure,' yet the CVSS vector asserts I:H and A:H (integrity and availability impact) - a pure information-disclosure issue would not carry those, so treat the tag as likely understating true impact and confirm the actual effect against the HPE advisory.

Exploit ScenarioDerived

An unauthenticated attacker with network access to an iLO 7 management interface exploits the user-validation failure to bypass authentication and gain administrative control of the BMC. From that out-of-band foothold they can read sensitive data, alter firmware/server state, and power-cycle or disrupt the host - but the high attack complexity (AC:H) means success likely requires meeting specific preconditions rather than a single reliable request. No public exploit code has been identified at time of analysis.

Act Now Prioritize within 24-48h. Why: CRITICAL severity.
No patch listed yet 0.3% exploitation probability (EPSS)

Get an e-mail when this CVE is exploited, patched or re-scored. Free account.

Alert me

AnalysisAIv1 – Oct 05, 2026

Remote user validation in HPE Integrated Lights-Out (iLO) 7 firmware can be subverted by unauthenticated network attackers, giving them high-impact confidentiality, integrity, and availability effects on the baseboard management controller and, because the CVSS vector carries a scope change (S:C), potentially on the systems that controller manages. The flaw is rated CVSS 3.1 9.0 (AV:N/AC:H/PR:N/UI:N/S:C/C:H/I:H/A:H); the high attack complexity means a successful bypass hinges on specific preconditions, state, or timing rather than one deterministic request, and reachability is limited to networks that can route to the iLO management interface. No public exploit code has been identified at time of analysis and there is no CISA KEV listing, so real-world risk concentrates in environments where iLO is exposed beyond a segmented out-of-band management network.

RemediationAI

The provided intelligence does not identify a fixed iLO 7 firmware build, so the first step is to confirm the vendor's remediation guidance and any corrected firmware version in the HPE security bulletin at https://support.hpe.com/hpesc/public/docDisplay?docId=hpesbhf05163en_us&docLocale=en_US and then apply that firmware update through the iLO update mechanism (or offline via the management channel if remote update paths are considered untrusted); do not assume a patched build exists until the advisory names one. Until a fix is confirmed and deployed, restrict network reachability to the iLO interface as the primary compensating control: place iLO on a dedicated, isolated out-of-band management VLAN or separate physical network, block inbound access from user networks and the internet at the firewall or upstream router, and permit management sessions only from a hardened bastion or jump host with tightly scoped source-address rules. These controls have real trade-offs - full isolation means administrators must reach iLO through a jump host or local console, which slows incident response and can itself become a single point of failure if not redundant - so pair them with iLO audit logging and alerting on unexpected authentication attempts or session creation, and rotate iLO credentials and certificates on any controller that may have been reachable while unpatched. Because no public exploit code has been identified at time of analysis, there is no urgent need for exploit-specific detection signatures, but the network-segmentation measures remain warranted given the 9.0 base score and the scope-change impact on managed hosts.

Affected VersionsENISA

HPE Integrated Lights-Out (iLO) 7 1.25.00

Affected Packages

euvd hpe_integrated_lights_out_ilo_7 no fix

Source: OSV (Open Source Vulnerabilities)

Affects your stack

Affects 1 package in euvd

Checking this CVE against your own stacks and servers is part of the Basic plan and up.

Technical ContextAI · show details

HPE Integrated Lights-Out 7 is the seventh-generation embedded baseboard management controller (BMC) firmware for HPE iLO 7 platforms, an out-of-band management stack that exposes a web/remote interface for console access, power control, virtual media, and firmware management. The reported defect is a remote user validation failure, i.e. a weakness in the authentication/access-control logic that validates remote users before granting management sessions; no CWE identifier was assigned in the source data, so any mapping to authentication-bypass classes such as CWE-287/288 would be analyst inference rather than a vendor classification. The CVSS metrics are informative: PR:N and UI:N mean the validation step can be attacked without credentials or victim interaction, AC:H signals that the failure is condition-dependent (likely requiring a particular state, sequence, or timing window), and S:C indicates that impact is assessed as extending past the BMC itself to downstream managed hosts. The accompanying tag characterizes the outcome as information disclosure, consistent with a validation bypass that leaks protected management data, though the vector's I:H and A:H indicate broader compromise potential. The CPE entry cpe:2.3:a:hewlett_packard_enterprise_(hpe):hpe_integrated_lights-out_(ilo)_7:*:*:*:*:*:*:*:* pins the affected technology to iLO 7 firmware with no version constraint, meaning the wildcard covers all releases until HPE specifies otherwise.

Know when Hpe Integrated Lights Out Ilo 7 gets its next vulnerability

  • Watch products and get an email when something new is published
  • Check this CVE against your own stack and servers
  • Exploit and PoC references, threat intelligence from 22 sources

No credit card · 7-day full trial

Severity by source

Vendor (hpe) PRIMARY 9.0 CRITICAL
AV:N/AC:H/PR:N/UI:N/S:C/C:H/I:H/A:H
vuln.today AI 9.0 CRITICAL

Unauthenticated network-reachable BMC validation bypass (AV:N/PR:N/UI:N) with condition-dependent triggering (AC:H); compromising iLO changes scope to the managed host, yielding full C/I/A impact.

3.1 AV:N/AC:H/PR:N/UI:N/S:C/C:H/I:H/A:H
4.0 AV:N/AC:H/AT:N/PR:N/UI:N/VC:H/VI:H/VA:H/SC:L/SI:L/SA:L

Primary rating from Vendor (hpe).

CVSS VectorVendor: hpe

Attack Vector
Network
Attack Complexity
High
Privileges Required
None
User Interaction
None
Scope
Changed
Confidentiality
High
Integrity
High
Availability
High

DescriptionCVE.org

A remote user validation failure vulnerability exists in HPE Integrated Lights-Out (iLO) 7 firmware.

Executive ViewAI

Why It Matters

HPE Integrated Lights-Out (iLO) 7 firmware contains a critical unauthenticated vulnerability that could allow attackers to compromise the baseboard management controller and potentially the servers it manages. No public exploit identified at time of analysis; no vendor-released patch identified at time of analysis. Organizations with iLO interfaces reachable from untrusted networks face significant risk of data breaches, service outages, or unauthorized system changes, and leadership should prioritize immediate network isolation of iLO management interfaces.

Business Impact: Severe
Compensating Controls

Network segmentation and strict access controls to limit reachability to the iLO management interface to trusted out-of-band networks only.

Threat Intelligence Overview

EPSS Score
0.3%
Top 83% exploitable
Prevalence
Medium
iLO 7 is HPE's newest BMC generation (Gen12), growing but not yet widely deployed
Data Quality
6 sources
Confidence: High

How this decision was reached

The engine reads each signal below and applies a fixed list of rules from top to bottom. The first rule that matches sets the recommended action – like a statement, every line is shown.

SignalValue
Severity CRITICAL
CISA KEV No
Public POC No
EPSS 0.3%
Patch available No
Active threat No
Deciding rule
CRITICAL severity
What every action level means
Emergency Immediate action required. Criteria: CRITICAL + in CISA KEV (actively exploited) without patch, OR CRITICAL + EPSS > 30% without patch, OR CRITICAL + active threat signals without patch.
Act Now Prioritize within 24-48h. Criteria: in KEV with patch available, OR CRITICAL + public POC, OR HIGH + EPSS > 10%, OR CRITICAL + active threat, OR any CRITICAL severity.
This Week Schedule remediation this week. Criteria: HIGH severity (CVSS 7.0-8.9). Patch within normal change window.
This Month Plan within 30 days. Criteria: MEDIUM severity (CVSS 4.0-6.9), lower exploitation probability. Include in regular patch cycle.
Monitor Track and reassess. Criteria: LOW severity (CVSS 0.1-3.9), minimal exploitation risk. No immediate action needed.

SSVC AssessmentENISA

SSVC Decision
Scheduled
Exploitation
None
System Exposure· derived
Open
Automatable
No
Human Impact
Very High
Technical Impact
Total

Priority Score

45
Low Medium High Critical
KEV: 0
EPSS: 0
CVSS: +45
PoC: 0
Weaponized: 0
Threat intel: 0
Gov advisory: 0

Attack Technique

Authentication bypass attacks exploit flaws in the verification mechanisms that control access to systems and applications.

This site uses cookies essential for authentication and security. No tracking or analytics cookies are used. Privacy Policy