CVE-2026-23596VulnerabilityPublished 17 Feb 2026

CVE-2026-23596: Hewlett Packard Enterprise (HPE) HPE Aruba Networking Private 5G Core · Vulnerability

Affects Hewlett Packard Enterprise (HPE) HPE Aruba Networking Private 5G CoreSource CVE Database V5

Not known to be exploited · CVSS 6.5 Medium.

Data as of 25 Oct 2026, 19:02 UTC

CVSS 3.1 base score

6.5Medium

How severe the flaw is on the 0–10 CVSS scale.

EPSS: 0.2% chance of exploitation in 30 days – higher than 18% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.

CVSS:3.1/AV:A/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H

Attack Vector: Adjacent
Attack Complexity: Low
Privileges Required: None
User Interaction: None
Scope: Unchanged
Confidentiality: None
Integrity: None
Availability: High

Bold values are the worst case: easiest to exploit or largest impact.

Attack Vector: Adjacent: The vulnerable component is bound to the network stack, but the attack is limited at the protocol level to a logically adjacent topology. This can mean an attack must be launched from the same shared physical (e.g., Bluetooth or IEEE 802.11) or logical (e.g., local IP subnet) network, or from within a secure or otherwise limited administrative domain (e.g., MPLS, secure VPN to an administrative network zone).
Attack Complexity: Low: Specialized access conditions or extenuating circumstances do not exist. An attacker can expect repeatable success against the vulnerable component.
Privileges Required: None: The attacker is unauthorized prior to attack, and therefore does not require any access to settings or files to carry out an attack.
User Interaction: None: The vulnerable system can be exploited without any interaction from any user.
Scope: Unchanged: An exploited vulnerability can only affect resources managed by the same security authority. In this case, the vulnerable component and the impacted component are either the same, or both are managed by the same security authority.
Confidentiality: None: There is no loss of confidentiality within the impacted component.
Integrity: None: There is no loss of integrity within the impacted component.
Availability: High: There is total loss of availability, resulting in the attacker being able to fully deny access to resources in the impacted component; this loss is either sustained (while the attacker continues to deliver the attack) or persistent (the condition persists even after the attack has completed). Alternatively, the attacker has the ability to deny some availability, but the loss of availability presents a direct, serious consequence to the impacted component (e.g., the attacker cannot disrupt existing connections, but can prevent new connections; the attacker can repeatedly exploit a vulnerability that, in each instance of a successful attack, leaks a only small amount of memory, but after repeated exploitation causes a service to become completely unavailable).

Definitions: FIRST CVSS v3.1 specification.

Exploitation evidence

Disclosed: evidence found.
CVE published 17 Feb 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 2026-10-25.

Disclosed: The CVE record is public on cve.org. Its publication is t = 0.
Detectable: A public nuclei template can find exposed instances, for defenders and attackers alike.
Weaponised: Public exploit code exists in Metasploit or Exploit-DB, or CISA SSVC reports a public proof of concept.
Exploited in the wild: CISA KEV lists it, CISA SSVC rates exploitation active, or a source reports attacks.
Observed by OffSeq Mirage: OffSeq Mirage honeypot sensors recorded attack traffic for this CVE, or found exposed hosts without attack traffic.

Moments are spaced evenly, not to scale; a dashed line marks a gap of six months or more. Deltas count from t = 0. Sources that give only a date (CISA KEV, Exploit-DB, or a time of exactly 00:00Z) read “same day” rather than hours. Metasploit modules carry the flaw’s disclosure date, not their release date, and nuclei templates carry no date, so both appear above but not on the timeline.

What to do

Affected software

Product	Affected	Fixed in
Hewlett Packard Enterprise (HPE)HPE Aruba Networking Private 5G Core	Affected >=1.24.3.0 <=1.24.3.4	Fixed in–

AI-suggested

1. Apply vendor patches or updates as soon as Hewlett Packard Enterprise releases them for the affected Aruba Networking Private 5G Core version 1.24.3.0. 2. Restrict network access to the management API by implementing strict network segmentation and firewall rules, allowing only trusted management hosts to communicate with the API. 3. Employ VPNs or secure tunnels for management traffic to prevent unauthorized network access. 4. Monitor network traffic and logs for unusual activity targeting the management API, including repeated service restart attempts or anomalous API calls. 5. Implement intrusion detection/prevention systems (IDS/IPS) with signatures or heuristics to detect exploitation attempts. 6. Conduct regular security assessments and penetration testing focused on private 5G infrastructure to identify and remediate exposure. 7. Develop and test incident response plans specifically addressing private 5G service disruptions. 8. Limit the exposure of management interfaces to the internet or untrusted networks to reduce attack surface. 9. Maintain up-to-date asset inventories to quickly identify affected systems and prioritize remediation. These measures go beyond generic advice by focusing on network-level controls, monitoring, and operational readiness tailored to private 5G core environments.

Description

A vulnerability in the management API of the affected product could allow an unauthenticated remote attacker to trigger service restarts. Successful exploitation could allow an attacker to disrupt services and negatively impact system availability.

Impact

For European organizations, the impact of CVE-2026-23596 centers on potential denial of service against private 5G core network infrastructure. Enterprises and critical infrastructure operators relying on HPE Aruba Networking Private 5G Core for secure, low-latency wireless connectivity could experience service outages, disrupting business operations, industrial automation, or emergency communications. The disruption of private 5G services could affect manufacturing plants, logistics hubs, healthcare facilities, and smart city deployments that depend on continuous network availability. While confidentiality and data integrity remain unaffected, the loss of availability could lead to operational downtime, financial losses, and reputational damage. Given the increasing adoption of private 5G in Europe, especially in sectors like automotive, manufacturing, and public safety, the vulnerability poses a tangible risk. Additionally, the unauthenticated nature of the exploit means that attackers with network access—potentially insiders or lateral movement from compromised systems—could cause disruptions without needing credentials. The absence of known exploits in the wild currently limits immediate risk, but the vulnerability should be addressed promptly to prevent future exploitation.

CWE-400Uncontrolled Resource Consumption (opens in a new tab)
Class weaknessLikelihood of exploit: High
The product does not properly control the allocation and maintenance of a limited resource.
MITRE discourages mapping vulnerabilities to this broad entry; the root cause is usually a more specific weakness.
Architecture and Design
Design throttling mechanisms into the system architecture. The best protection is to limit the amount of resources that an unauthorized user can cause to be expended. A strong authentication and access control model will help prevent such attacks from occurring in the first place.
Architecture and Design
Mitigation of resource exhaustion attacks requires that the target system either: recognizes the attack and denies that user further access for a given amount of time, or; uniformly throttles all requests in order to make it more difficult to consume resources more quickly than they can again be freed.
Architecture and Design
Ensure that protocols have specific limits of scale placed on them.
OWASP Cheat Sheets
File Upload (opens in a new tab)
OWASP ASVS 4.0.3
V12.1.1 (opens in a new tab)
Attack patterns
XML Ping of the Death (opens in a new tab)
Regular Expression Exponential Blowup (opens in a new tab)
Sustained Client Engagement (opens in a new tab)
From MITRE CWE, MITRE CAPEC and OWASP (Top 10, OpenCRE).

References

support.hpe.com/hpesc/public/docDisplay?docId=hpesbnw05002en_us&docLocale=en_US (opens in a new tab)

Community reviews

Loading reviews…

Exploitation evidence

What to do

Affected software

Description

AI analysisMachine-generated, updated 18 Feb 2026, 08:34 UTC

WeaknessesCWE-400

Technical details

References

Community reviews

Related threats