← Search results
CVE-LINKED INVENTORY5 SECURITY RECORDS
Hewlett Packard Enterprise (HPE)
HPE Aruba Networking Private 5G Core
Affected and fixed version statements observed in the public BlackTree CVE catalogue. These statements describe vulnerability scope, not publisher support entitlement.
This identity is present in BlackTree CVE records, but no product-specific publisher support or retirement history is currently registered in Lifecycle.
A missing support date does not mean the product is supported. CVE publication dates and affected-version ranges must not be interpreted as EOL dates.
CVE-observed version history
| CVE | Published | Affected versions | Fixed version information | Publisher evidence |
|---|---|---|---|---|
| CVE-2026-23598 | 17 Feb 2026 | 1.24.3.0 ≤ 1.24.3.4 | To resolve the vulnerabilities described above, it is recommended to upgrade the software to HPE Aruba Networking Private 5G Core 1.25.1.0 and above. The latest version of the product is available for download at https://myenterpriselicense.hpe.com/. HPE Aruba Networking does not evaluate or patch HPE Aruba Networking Private 5G Core Software versions that have reached their End of Support (EoS) milestone. For more information about HPE Aruba Networking Product Lifecycle and versioning policy, please visit: https://www.hpe.com/psnow/doc/4aa5-5978enw?jumpid=in_pdfviewer-psnow. | Update reference ↗ |
| CVE-2026-23597 | 17 Feb 2026 | 1.24.3.0 ≤ 1.24.3.4 | To resolve the vulnerabilities described above, it is recommended to upgrade the software to HPE Aruba Networking Private 5G Core 1.25.1.0 and above. The latest version of the product is available for download at https://myenterpriselicense.hpe.com/. HPE Aruba Networking does not evaluate or patch HPE Aruba Networking Private 5G Core Software versions that have reached their End of Support (EoS) milestone. For more information about HPE Aruba Networking Product Lifecycle and versioning policy, please visit: https://www.hpe.com/psnow/doc/4aa5-5978enw?jumpid=in_pdfviewer-psnow. | Update reference ↗ |
| CVE-2026-23596 | 17 Feb 2026 | 1.24.3.0 ≤ 1.24.3.4 | To resolve the vulnerabilities described above, it is recommended to upgrade the software to HPE Aruba Networking Private 5G Core 1.25.1.0 and above. The latest version of the product is available for download at https://myenterpriselicense.hpe.com/. HPE Aruba Networking does not evaluate or patch HPE Aruba Networking Private 5G Core Software versions that have reached their End of Support (EoS) milestone. For more information about HPE Aruba Networking Product Lifecycle and versioning policy, please visit: https://www.hpe.com/psnow/doc/4aa5-5978enw?jumpid=in_pdfviewer-psnow. | Update reference ↗ |
| CVE-2026-23595 | 17 Feb 2026 | 1.24.3.0 ≤ 1.24.3.4 | To resolve the vulnerabilities described above, it is recommended to upgrade the software to HPE Aruba Networking Private 5G Core 1.25.1.0 and above. The latest version of the product is available for download at https://myenterpriselicense.hpe.com/. HPE Aruba Networking does not evaluate or patch HPE Aruba Networking Private 5G Core Software versions that have reached their End of Support (EoS) milestone. For more information about HPE Aruba Networking Product Lifecycle and versioning policy, please visit: https://www.hpe.com/psnow/doc/4aa5-5978enw?jumpid=in_pdfviewer-psnow. | Update reference ↗ |
| CVE-2025-37100 | 10 Jun 2025 | 1.24.1.0 ≤ 1.25.1.0 | To resolve the vulnerability described above, it is recommended to upgrade the software to the following version: - HPE Aruba Networking Private 5G Core 1.25.1.1 and above HPE Aruba Networking does not evaluate or patch HPE Aruba Networking Private 5G Core Software versions that have reached their End of Support (EoS) milestone. For more information about HPE Aruba Networking Product Lifecycle and versioning policy, please visit: https://www.hpe.com/psnow/doc/4aa5-5978enw?jumpid=in_pdfviewer-psnow | Update reference ↗ |
How this record is maintained
The CVE inventory is reconciled automatically from cve.blacktree.nl. Exact identity matches link to existing Lifecycle product or package histories. Unmatched products stay in a prioritised publisher-source research queue, and Lifecycle marks the date gap instead of inferring a support boundary from vulnerability data.