Device Support-Lifespan Observatory

What vendors do, not what they announce.

TP-Link

CPE510 v3.28

Actively updated well evidenced

firmware is arriving about as often as it always has

300 days since the last release against a median gap of 494 (0.6x)

Sign in to be emailed when this verdict changes.
Last firmware
4 December 2025 (10 months ago)
Releases seen
5
Update rhythm
about every 1 year
Support observed
≥5 years
Vendor's promise
no support period we can evaluate
Patch latency
not measurable — its changelogs name no CVE ids

Which one do I have?

TP-Link ships this model in more than one hardware revision, and they do not share firmware. The revision is printed on the label on the underside, usually after the model — Ver 1.0, V4.6. Getting it wrong is the easiest way to read the wrong answer here.

Firmware history

  1. CPE510(US)_V3.28_2.3.3 Build 20251112 4 December 2025

    Release notes — disclosure 0.57
    Release Note > Version Info: 1. Minimum FW Version for Update: 2.3.2 Build 20251113 Rel.54430. 2. This firmware upgrade is irreversible. Contact tp-link technical support if downgrade is required. 3. Recommended Pharos Control version 2.0.8 or above. Enhancements: 1. Encrypted the firmware and optimized the algorithm to enhance the overall security of the firmware. Minimum FW Version for Update: 2.3.2 Build 20251113 Rel.54430. This firmware upgrade is irreversible. Contact tp-link technical support if downgrade is required.
  2. CPE510(US)_V3.28_2.3.2 Build 20251113 3 December 2025

    Release notes — disclosure 0.64
    Release Note > Version Info: 1. This firmware upgrade is irreversible. Contact tp-link technical support if downgrade is required. 2. Recommended Pharos Control version 2.0.8 or above. New Features: 1. Added support for delivering credentials after a device is reset and adopted by Pharos Control. 2. Added support for configurable TLS cipher and suite switches, allowing the use of legacy TLS versions and older cipher suites. Enhancements: 1. Enhanced device security. 2. Optimized TLS encryption algorithms. 3. Improved SSL certificate handling. 4. Optimized SSH encryption algorithms and added brute-force protection. 5. Optimized SSID encryption policy by setting WPA2 as the default and removing WEP/TKIP options. 6. Improved SNMP get/set community mechanism with strong password policies. Bug fixed: 1. Fixed an issue where the previous password might be retained when changing an SSID's encryption method after switching operating modes. 2. Fixed an issue where certain configuration pages displayed abnormally. For full release note, please refer to TP-Link Official Website. This firmware upgrade is irreversible. Contact tp-link technical support if downgrade is required.
  3. CPE510(US)_V3.28_2.2.4 Build 20230616 6 July 2023

    Release notes — disclosure 0.23
    New Feature/Enhancement: 1. Optimized NTP mechanism.
  4. CPE510(US)_V3.28_2.2.3 Build 20230222 21 March 2023

    Release notes — disclosure 0.54
    New Feature/Enhancement: 1. Optimize security vulnerabilities. Bug Fixed: 1. Fixed the bug that BPDU packets will be dropped by the CPE in AP mode. 2. Fixed the bug that CPE works on the DFS channels stops working in some special wireless network environment. 3. Fixed the bug that the unstable power supply causes the CPE reset. 4. Fixed the bug that the CPE in Client mode cannot connect to a Deco with fast roaming enabled.
  5. CPE510(US)_V3.28_20200612 14 July 2020

    Cites CVE-2020-8597

    Release notes — disclosure 0.87
    New Features/Enhancements: 1. Optimized the SSID scan process. 2. Extended the SSL certificate validity to 2029. Bug Fixed: 1. Fixed the CVE-2020-8597 PPPoE security problem. 2. Fixed the bug that CPE may failed to connect with TP-Link Deco products.

Evidence

One archived page sits behind this record, the earliest read on 1 August 2026. Everything above was read from it, and each is kept byte for byte so it can be checked after the vendor edits the original.

Identifiers: marketing_name CPE510

Judged by lifecycle-1 on 30 September 2026. How these verdicts are computed.

Machine-readable: JSON · RSS