Attack ChainAIDerived
Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain
-
AccessReach product over network (AV:N)
-
ExploitSatisfy high-complexity precondition (AC:H)
-
ExecutionTrigger flaw without auth (PR:N/UI:N)
-
ImpactCompromise confidentiality, integrity and availability (C:H/I:H/A:H)
Vulnerability Assessment
| Weakness |
CWE
OWASP Top 10:2025
A05:2025 - Injection
ASVS 5.0
V1 - Encoding and Sanitization Code injection prevention, sandbox exec
MITRE ATT&CK
2 techniques across 2 tactics: Execution, Initial Access The technique list with ATT&CK links and the kill-chain view is part of the Basic plan and up. |
| Exploitation Conditions | The CVSS vector indicates remote, unauthenticated reachability with no user interaction (AV:N/PR:N/UI:N), but AC:H signals a required precondition that the available sources do not describe - the trigger is not described in the available input, so the specific feature, protocol, or configuration needed cannot be named. The limiting factor is this high-complexity condition, which must be satisfied for exploitation; the affected product and any configuration or version constraints are not stated in the input and must be confirmed from the HPE advisory (hpesbnw05162en_us). |
| Impact | The provided CVSS 3.1 vector (AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H, base 8.1 High) describes a network-reachable flaw requiring no privileges and no user interaction, but with high attack complexity (AC:H) and full compromise of confidentiality, integrity, and availability. The high-complexity metric is the main brake on real-world risk: it implies the attacker must win some non-trivial condition the available sources do not describe. The vuln.today priority is 'this_week', below act_now/emergency, so this is a near-term patching priority rather than an emergency. No EPSS score, no CISA KEV listing, and no PoC/exploit reference are present in the input, so there is no signal of active exploitation or available exploit code. Note a conflict between signals: the sole tag is 'Information Disclosure' (a confidentiality-only technique), yet the CVSS vector asserts I:H and A:H as well - the impact scope is broader than the tag suggests, and the true impact mechanism should be verified against the HPE advisory. No CVE description or CWE was supplied, so the vulnerability mechanism is unverified. Overall: a genuine high-severity issue worth prioritizing this week, tempered by AC:H and the absence of any exploitation evidence. |
| Exploit ScenarioDerived | A remote, unauthenticated attacker reaches the affected HPE networking product over the network and triggers the flaw to disclose sensitive data and potentially alter system state, achieving high confidentiality, integrity, and availability impact. The high attack complexity means the attacker must satisfy a condition not described in the available sources, so exploitation is not straightforward. No public exploit code or PoC reference is present in the input. |
Get an e-mail when this CVE is exploited, patched or re-scored. Free account.
Alert meAnalysisAIv1 – Oct 22, 2026
HPE has published advisory hpesbnw05162en_us for a network-reachable flaw tracked as CVE-2026-79887 that, per its CVSS 3.1 vector (8.1 High), can fully compromise confidentiality, integrity, and availability of the affected system. The specific product, version range, CWE class, and the precondition implied by the high attack complexity (AC:H) are not stated in the available input, so the exact feature or configuration an attacker must arrange remains unconfirmed and must be read from the HPE advisory. No CISA KEV listing, no public exploit code, and no EPSS score were supplied at time of analysis; the single-source tag labels the issue 'Information Disclosure', which is narrower than the total-impact vector and should be reconciled against the vendor advisory. Prioritization signal from vuln.today places this in the 'this_week' queue rather than act_now or emergency.
RemediationAI
The available input contains no fixed version, no patch reference, and no vendor workaround, so the patch status at time of analysis is that no vendor-released fix version has been identified from these sources; the HPE advisory at https://support.hpe.com/hpesc/public/docDisplay?docId=hpesbnw05162en_us&docLocale=en_US must be consulted to obtain the affected version matrix and any fixed firmware or software release, and any version number should be taken from that bulletin rather than assumed. Because the vector is AV:N/PR:N/UI:N, the exposure path is network-based and unauthenticated, so the only compensating control the supplied evidence supports is reducing network reachability to the affected component until the vendor's fixed release is applied, with the trade-off that legitimate remote users of that interface lose access; no other workaround, feature toggle, or configuration change is described in the available data, and the high-complexity precondition recorded by AC:H cannot be mitigated specifically until the advisory names it. Operators should also treat the 'Information Disclosure' tag as unconfirmed and verify from the bulletin whether the real impact is limited to data exposure or extends to the integrity and availability compromise indicated by the C:H/I:H/A:H vector, since that distinction changes containment priorities.
Affected VersionsENISA
Affected Packages
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
The assessed vector AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H describes a flaw reachable over the network with no privileges and no user interaction, scope unchanged, and high impact across confidentiality, integrity, and availability. The AC:H metric records a condition that must be met before exploitation succeeds; the supplied sources do not say what that condition is, so the trigger, protocol, or configuration involved cannot be named here. CWE is not provided, so the root-cause class (memory corruption, injection, logic error, deserialization, and so on) is undetermined - the mechanism should not be inferred from the vector alone. No CPE strings were supplied, meaning the affected product family and version boundaries are unverified. Reported by security-alert@hpe.com with a single HPE support-document reference (docId hpesbnw05162en_us), the intelligence picture rests on one vendor source plus the NVD placeholder, and the 'Information Disclosure' tag is a single-source classification that sits uneasily against C:H/I:H/A:H and warrants confirmation.
Know when Hpe 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
AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H
No description was supplied, so metrics mirror the vendor-reported HPE vector: network vector, no privileges/interaction, high complexity, unchanged scope, and full CIA impact.
Primary rating from Vendor (hpe).
CVSS VectorVendor: hpe
DescriptionCVE.org
No description provided
Executive ViewAI
HPE has disclosed a high-severity network-reachable vulnerability (CVE-2026-79887, CVSS 8.1) affecting an unspecified product, with potential for full compromise of confidentiality, integrity, and availability. Leadership should care because a successful exploit could disrupt critical operations and expose sensitive data, though no active exploitation has been confirmed.
No vendor-released patch identified at time of analysis.
Threat Intelligence Overview
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.
What every action level means
SSVC AssessmentENISA
Priority Score
Attack Technique
Code injection occurs when an application accepts user input and passes it directly into a language interpreter or evaluator without proper sanitization.
Remote Code Execution represents the critical moment when an attacker successfully runs arbitrary code on a target system without physical access.
An unprivileged network attacker could gain system privileges to provisioned Intel manageability SKUs: Intel Active Mana
The read_mru_list function in NTP before 4.2.8p9 allows remote attackers to cause a denial of service (crash) via a craf
Default, hard-coded credentials shipped on several administrative and system accounts in HPE's Analytics and Location En
A directory traversal vulnerability in Hewlett Packard Enterprise Insight Remote Support may allow remote code execution
A potential security vulnerability has been identified in Hewlett Packard Enterprise OfficeConnect 1820, 1850, and 1920S
A security vulnerability in HPE Smart Update Manager (SUM) prior to version 8.5.6 could allow remote unauthorized access
A vulnerability in HPE Insight Remote Support (IRS) prior to v7.15.0.646 may allow an unauthenticated denial of service
NTP through 4.2.8p12 has a NULL Pointer Dereference. Rated high severity (CVSS 7.5), this vulnerability is remotely expl
A maximum-severity, network-reachable flaw (CVSS 3.1 base 10.0) in an as-yet-unnamed HPE product allows remote attackers
Unauthenticated network attackers can potentially achieve high confidentiality, integrity, and availability impact again
HPE security bulletin hpesbnw05162en_us documents a maximum-severity (CVSS 10.0) exposure in an HPE product that is not
HPE advisory hpesbnw05162en_us covers a product flaw carrying a CVSS 3.1 base score of 10.0 (AV:N/AC:L/PR:N/UI:N/S:C/C:H
EUVD-2026-108387
GHSA-c5vh-66mx-vhh3
NVD
CVE.org
EPSS
Vulnrichment
VulDB
Exploit-DB