Attack ChainAIDerived
Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain
-
AccessReach product over network (AV:N)
-
ExploitSend crafted request (AC:L, no auth)
-
ExecutionTrigger disclosure/tamper flaw
-
ImpactExfiltrate sensitive data or alter state
Vulnerability Assessment
| Exploitation Conditions | No CVE description was provided, so the exact required feature, protocol, or configuration cannot be named from the available sources. Based only on the supplied CVSS vector (AV:N/AC:L/PR:N/UI:N), exploitation would be remote, unauthenticated, and require no user interaction against a network-reachable interface of the affected HPE networking product. Limiting factors cannot be confirmed from the input: the affected product, versions, whether a non-default mode is required, and which network interface must be exposed are all unspecified and must be verified against HPE advisory hpesbnw05162en_us. |
| Impact | Signals point in a serious direction but rest on thin evidence. The vendor-supplied CVSS 3.1 vector (AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:L, base 9.4) describes a network-reachable, low-complexity flaw needing no privileges and no user interaction - the profile of a high-priority remote vulnerability - and the vuln.today Decision label is act_now, which signals this should be treated as urgent rather than deferred. However, several key signals are MISSING: no EPSS exploitation-probability score is provided, there is no CISA KEV listing in the input, and no POC or exploit reference is present (only the HPE advisory itself). There is also a CONFLICT to verify: the sole classification tag is 'Information Disclosure' (a confidentiality concern), yet the CVSS vector claims High integrity impact (I:H) and Low availability impact (A:L) in addition to High confidentiality (C:H) - pure information disclosure would normally be C:H/I:N/A:N, so either the tag understates the impact or the vector overstates it; verify the actual impact scope with the HPE advisory. Finally, no CVE description was provided, so the exploitation mechanism cannot be independently confirmed - the trigger is not described in the available sources. Net: treat as act_now per the decision label and the unauthenticated-network CVSS profile, but confirm affected product, versions, and true impact against the HPE bulletin before drawing firm conclusions. |
| Exploit ScenarioDerived | Per the CVSS vector, a remote attacker with no credentials sends crafted network traffic to an affected HPE networking product and, without any user interaction, obtains sensitive information and/or alters data (C:H, I:H). The exact mechanism is not described in the available sources, and no public exploit code is referenced. The low attack complexity (AC:L) means that once a working request is known, exploitation would be straightforward and repeatable. |
Get an e-mail when this CVE is exploited, patched or re-scored. Free account.
Alert meAnalysisAIv1 – Oct 22, 2026
A critical-severity (CVSS 9.4) flaw affects an as-yet-unnamed HPE networking product, exposed through a network-reachable interface that remote attackers can reach without authentication or user interaction (AV:N/AC:L/PR:N/UI:N), with high confidentiality and integrity impact and a lesser availability impact. The only public reference is HPE advisory hpesbnw05162en_us, and no CVE description, CWE classification, or CPE data was supplied, so the affected product family, version ranges, and the specific interface involved remain unconfirmed. Third-party triage assigns this an act_now priority, but no public exploit code and no CISA KEV entry are associated with the record at time of analysis, so the urgency rests on the severity vector and the vendor's own security-alert notification rather than on observed exploitation.
RemediationAI
No fixed version, patch identifier, or upgrade path is given in the supplied data, so patch status is unconfirmed rather than negative; the primary action is to open HPE Security Bulletin hpesbnw05162en_us (https://support.hpe.com/hpesc/public/docDisplay?docId=hpesbnw05162en_us&docLocale=en_US) and follow the vendor's stated fixed firmware or software release for each affected platform, since HPE advisories are the only authoritative source for the version mapping here. Because the confirmed vector is AV:N/AC:L/PR:N/UI:N, the only compensating control the available evidence directly supports is reducing network reachability of the affected interface to trusted management networks or hosts while the fixed release is identified - the trade-off being loss of remote administrative access for legitimate operators, so scope any such restriction to the specific interface HPE names rather than blackholing the device. Do not treat generic hardening as a substitute for the vendor fix, and do not assume a workaround exists: the supplied sources neither confirm nor deny one, and HPE's bulletin is where any interim mitigation, including whether updating is the only complete remediation, would be stated.
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
No CWE identifier accompanies this record, so the root-cause class cannot be stated; the trigger, the vulnerable code path, and the protocol or service involved are not described in the available sources. What the supplied CVSS:3.1 vector does establish is the exploitation profile: network vector, low attack complexity, no privileges required, and no user interaction, with scope unchanged and a high-high-low confidentiality/integrity/availability split. The single tag on the record reads 'Information Disclosure', which is only partly aligned with a vector that scores high integrity impact as well, suggesting either that the disclosure of data enables further manipulation or that the tag is a coarse classification of the advisory rather than of the flaw's full effect. The reporting address (security-alert@hpe.com) and the HPE Support Center document identifier hpesbnw05162en_us place the disclosure within HPE's own security bulletin process, which is the authoritative technical source; nothing in the supplied material indicates whether a non-default configuration, a specific management plane, or a particular firmware branch is required. Because neither the product nor the interface is confirmed, any claim about the exact attack surface would be inference rather than evidence.
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:L/PR:N/UI:N/S:U/C:H/I:H/A:L
No description exists to independently diverge from the vendor vector; I retain AV:N/AC:L/PR:N/UI:N and the vendor-assigned C:H/I:H/A:L, noting the 'Information Disclosure' tag only corroborates the confidentiality impact.
Primary rating from Vendor (hpe).
CVSS VectorVendor: hpe
DescriptionCVE.org
No description provided
Executive ViewAI
A critical vulnerability (CVSS 9.4) has been identified in an unspecified HPE networking product, which could allow remote unauthenticated attackers to compromise confidentiality and integrity. Although no exploitation has been observed, the severity and network-reachability warrant immediate leadership attention to identify and protect affected systems.
No vendor-released patch identified at time of analysis; implement network segmentation, restrict access to management interfaces, and monitor for suspicious activity.
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
Information disclosure occurs when an application unintentionally exposes sensitive data that aids attackers in reconnaissance or directly compromises security.
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-108372
GHSA-3r73-gmqf-px5q
NVD
CVE.org
EPSS
VulDB
Exploit-DB