Question 1

What is the EOL Risk Score for HPE Aruba Networking gateways and controllers (hardware) JW638A (Aruba 7005 (IL) FIPS/TAA-compliant 4-port 10/100/1000BASE-T 16 AP and 1K Client Controller)?

Accepted Answer

HPE Aruba Networking gateways and controllers (hardware) JW638A (Aruba 7005 (IL) FIPS/TAA-compliant 4-port 10/100/1000BASE-T 16 AP and 1K Client Controller) has an EOL Risk Score™ of 10 out of 100, placing it in the Low risk band. The score is calculated from four factors: EOL Recency (0/40), Attack Surface (10/30), CISA KEV Exposure (0/20), and Extended Support Availability (0/10).

Question 2

Is HPE Aruba Networking gateways and controllers (hardware) JW638A (Aruba 7005 (IL) FIPS/TAA-compliant 4-port 10/100/1000BASE-T 16 AP and 1K Client Controller) still supported?

Accepted Answer

HPE Aruba Networking gateways and controllers (hardware) JW638A (Aruba 7005 (IL) FIPS/TAA-compliant 4-port 10/100/1000BASE-T 16 AP and 1K Client Controller) is currently supported. End of life is scheduled for April 30, 2028. Plan your migration before that date to avoid security risk.

Question 3

When does HPE Aruba Networking gateways and controllers (hardware) JW638A (Aruba 7005 (IL) FIPS/TAA-compliant 4-port 10/100/1000BASE-T 16 AP and 1K Client Controller) reach end of life?

Accepted Answer

HPE Aruba Networking gateways and controllers (hardware) JW638A (Aruba 7005 (IL) FIPS/TAA-compliant 4-port 10/100/1000BASE-T 16 AP and 1K Client Controller) reached (or will reach) end of life on April 30, 2028. After this date, no security patches or bug fixes are issued by the vendor.

Question 4

What are the security risks of running HPE Aruba Networking gateways and controllers (hardware) JW638A (Aruba 7005 (IL) FIPS/TAA-compliant 4-port 10/100/1000BASE-T 16 AP and 1K Client Controller) after end of life?

Accepted Answer

After end of life, HPE Aruba Networking gateways and controllers (hardware) JW638A (Aruba 7005 (IL) FIPS/TAA-compliant 4-port 10/100/1000BASE-T 16 AP and 1K Client Controller) no longer receives security patches. Any newly discovered CVEs remain unpatched indefinitely. Organizations running EOL software also face compliance violations under SOC 2, PCI DSS, HIPAA, and ISO 27001, which require use of supported software versions.