Improper Authentication Rate Limiting on TP-Link's Archer C64

published 2026-05-28 5 mo ago modified 2026-10-26 13 d ago also EUVD-2026-32929

cvss: 8.8; 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

Due to improper enforcement of authentication rate-limiting on a debug SSH service in Archer C64 v1, the SSH service allows unlimited authentication attempts and uses the same credentials as the web interface. This enables an attacker to brute-force valid credentials via SSH.

Successful exploitation could allow an attacker with adjacent network access to obtain administrative credentials through unrestricted authentication attempts and subsequently gain full administrative access to the device, impacting system confidentiality, integrity, and availability.

Patch / fix

fixed in 1 links 1

TP-Link Systems Inc. Archer C64 v1.0 1.15.0 Build 250729 Rel.63489n(4555)

tp-link.com/en/support/download/archer-c64/v1/#Firmware patch

CISA SSVC

Exploitation: none
Automatable: no
Technical impact: total
Assessed: 5 mo ago (2026-05-28)

Exploit prediction

0.51% 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	8.7	CVSS:4.0/AV:A/AC:L/AT:N/PR:N/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N
CNA	4.0	8.7	CVSS:4.0/AV:A/AC:L/AT:N/PR:N/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.8	CVSS:3.1/AV:A/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H

Affected products

TP-Link Systems Inc. Archer C64 v1.0

Classification

Weakness

CWE-288 Authentication Bypass Using an Alternate Path or Channel
CWE-306 Missing Authentication for Critical Functionality

References

tp-link.com /en/support/download/archer-c64/v1/#Firmware
patch, product
tp-link.com /us/support/faq/5105/
vendor-advisory

Sources

CVE List CVE-2026-8697
NVD CVE-2026-8697

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.

Summary