Stack-based buffer overflow in TP-Link Archer AX55 v4

Why this deserves its current priority

A CVSS score is not reported in the current record. The current sources do not mark it as known exploited. Treat this as a source-backed prioritization signal, not a statement about your environment.

Affected scope and exposure questions

The current feed maps TP-Link Systems Inc./Archer AX55 v4 (generic). Check affected ranges and fixed versions before updating.

Recommended response

1. 1Check inventory. Check lockfiles and deployed manifests for TP-Link Systems Inc./Archer AX55 v4.
2. 2Review the reported fix. Update TP-Link Systems Inc./Archer AX55 v4 to 1.2.1 Build 20260527 if you use the affected versions. Test the change in a non-production environment first.

Evidence timeline and material changes

1. Published upstream

   Sep 3, 2026

   Evidence: source:cvelist:source_dates:source-dates:record

2. Source modified

   Sep 3, 2026

   Evidence: source:cvelist:source_dates:source-dates:record

3. First seen by HOL

   Sep 3, 2026

Sources and claim methodology

• Source referencetp-link.com
• Source referencetp-link.com

Related CVEs

• Hardcoded Shared RSA-1024 Private Key in TP-Link Archer AX55 v4Same tp-link systems inc./archer ax55 v4 package
• Out Of Bounds Write parsing a .DSB file in DASYLab due to lack of proper validation of user-supplied dataSame generic ecosystem
• Out Of Bounds Write when parsing a .DSB file in DASYLab due to improper validation of user-supplied data, resulting in a write past the end of an allocated heapSame generic ecosystem
• Out Of Bounds Write when parsing a .DSB file in DASYLab due to improper validation of user-supplied data, resulting in a write past the end of an allocated data structureSame generic ecosystem
• Out Of Bounds Read in file handling when parsing a .DSB file in DASYLabSame generic ecosystem
• Out Of Bounds Read outside the bounds of an allocated data structure when parsing a .DSB file in DASYLabSame generic ecosystem