Threadlinqs IntelligenceStart free

Vendor1 product tracked

Hewlett Packard Enterprise (HPE) vulnerabilities & exploitation

5 with public exploit

As of 2026-10-25, Threadlinqs tracks 16 Hewlett Packard Enterprise (HPE) CVEs, 0 in the CISA Known Exploited Vulnerabilities catalog, linked to 2 tracked threat campaigns.

CVEs
16Since 2026
CISA KEV
00% of CVEs
Critical
2CVSS v3 9.0+
Avg CVSS
8.4/10Max 9.8
Threats
2Linked campaigns
Actors
0None attributed

Data as of:

Exploitation timeline

Threadlinqs has recorded 16 Hewlett Packard Enterprise (HPE) CVEs published between and . The busiest month was 2026-09 (11 new CVEs). None of them is listed in CISA KEV yet.

Most exploited vulnerabilities

Ranked with CISA KEV listings first, then EPSS exploit probability, then CVSS score. Showing 16 of 16 tracked Hewlett Packard Enterprise (HPE) CVEs.

Products affected

Threadlinqs normalises CPE and CNA product records across all 16 CVEs; 1 distinct Hewlett Packard Enterprise (HPE) product is affected. The most frequently affected:

  • AOS-CX 16 CVEs

Threat activity

2 tracked threat campaigns reference Hewlett Packard Enterprise (HPE) products or exploit Hewlett Packard Enterprise (HPE) CVEs:

How to prioritise Hewlett Packard Enterprise (HPE) patching

This order follows the data Threadlinqs holds for Hewlett Packard Enterprise (HPE), not a generic severity checklist:

  • No Hewlett Packard Enterprise (HPE) CVE is in CISA KEV yet, so rank by exploit probability instead.
  • Outside KEV, the highest EPSS scores are CVE-2026-23816 (1.2%), CVE-2026-23815 (1%), CVE-2026-73749 (0.8%).
  • 2 CVEs score Critical and 13 High on CVSS v3 (maximum 9.8, average 8.4); sequence these after KEV and high-EPSS items.
  • 5 CVEs have a public exploit or proof of concept recorded, which shortens the time from disclosure to attack.

About this data

Vendor attribution comes from the CNA and CPE product records of each CVE, folded to one vendor name; CVSS, EPSS and KEV status are read from the Threadlinqs CVE catalog; campaign and actor links come from tracked threat records. Counts reflect the data as of 2026-10-25 and refresh daily.