CVE-2025-61983 json
Heap-based Buffer Overflow Vulnerability in TP-Link Archer AX53
published 2026-02-03 9 mo ago modified 2026-06-17 4 mo ago also EUVD-2025-206669
- cvss
- 8.0
- version 3.1, NVD
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 0.5%
- EPSS 0.5% chance of exploitation in 30 days, percentile 43%
- public exploits
- 0
- none known
Summary
Heap-based Buffer Overflow vulnerability in TP-Link Archer AX53 v1.0 (tmpserver modules) allows authenticated adjacent attackers to cause a segmentation fault or potentially execute arbitrary code via a specially crafted network packet containing an excessive number of fields with zero‑length values.This issue affects Archer AX53 v1.0: through 1.3.1 Build 20241120.
Patch / fix
CISA SSVC
- Exploitation
- none
- Automatable
- no
- Technical impact
- total
- Assessed
- 9 mo ago
Exploit prediction
0.50% chance of exploitation in the next 30 days, higher than 43% of all scored CVEs (FIRST EPSS, 2026-11-08).
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| CNA | 4.0 | 7.3 | CVSS:4.0/AV:A/AC:H/AT:N/PR:H/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N |
| CNA | 4.0 | 7.3 | CVSS:4.0/AV:A/AC:H/AT:N/PR:H/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X |
| NVD | 3.1 | 8.0 | CVSS:3.1/AV:A/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H |
Affected products
- TP-Link Systems Inc. Archer AX53 v1.0
Classification
- Weakness
-
- CWE-122 Heap-based Buffer Overflow
References
-
tp-link.com
/en/support/download/archer-ax53/v1/#Firmware
patch, product
-
tp-link.com
/my/support/download/archer-ax53/v1/#Firmware
patch, product
-
tp-link.com
/us/support/faq/4943/
vendor-advisory
-
talosintelligence.com
/vulnerability_reports/
third-party-advisory
- talosintelligence.com /vulnerability_reports/TALOS-2025-2286
Sources
- CVE List CVE-2025-61983
- NVD CVE-2025-61983
Fencer Vulns keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.