dbcve.org
Archer C64 FirmwareOperating system · Tp Link

CVE-2026-8697

HIGH · 8.8 CVSS v3.1 Published 2026-05-28
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
93/100
Remediation priority · Urgent
No privileges Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
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.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

The TP-Link Archer C64 v1 router contains a debug SSH service that lacks authentication rate-limiting, allowing unlimited login attempts. Since the SSH service reuses the same credentials as the web interface, attackers with adjacent network access can brute-force administrative credentials and gain full device control.

MitigationApply the vendor-supplied firmware update to patch the vulnerability. If no update is available, disable the debug SSH service via administrative controls or implement network segmentation to restrict access to the SSH port.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
Archer C64 FirmwareOperating system
Affected:= 1.15.0

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Adjacent
Complexity
Low
Privileges
None
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:A/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Identify the router firmware version
    Access the router web interface and navigate to System > Firmware Upgrade or Status page to view the current firmware version. Alternatively, check the label on the device or consult the router documentation for version lookup methods.
    Affected if The firmware version is 1.15.0, indicating the specific affected version.
  2. Determine if the debug SSH service is enabled
    Access the router administrative interface and look for SSH-related settings, typically under System Tools > SSH or Advanced > Network > SSH. Check if the SSH service is toggled on or enabled.
    Affected if The SSH service is enabled on the device, exposing the vulnerable debug service.
  3. Verify SSH port accessibility from the network
    From a system on the same network as the router, attempt to connect to the router's IP address on TCP port 22 (or run a port scan). Use command: telnet [router-ip] 22 or nmap -p 22 [router-ip]
    Affected if Port 22 (SSH) is open and reachable from an adjacent network segment, making the service exploitable.
  4. Check for SSH authentication rate-limiting
    Inspect the router SSH settings for any rate-limiting, lockout, or brute-force protection configuration options. If available, verify if a maximum failed attempts threshold or login delay is configured.
    Affected if No rate-limiting or brute-force protection is configured for SSH authentication, allowing unlimited login attempts.

A user is affected if the device runs firmware version 1.15.0, has the debug SSH service enabled, and the SSH port is accessible from the network without rate-limiting protection in place.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Apply the vendor-supplied firmware update to patch the vulnerability. If no update is available, disable the debug SSH service via administrative controls or implement network segmentation to restrict access to the SSH port.

Recommended fix Moderate confidence

Check TP-Link website for newer Archer C64 firmware version (later than 1.15.0)

  1. 1. Visit the official TP-Link support website at www.tp-link.com and navigate to the Archer C64 product page
  2. 2. Locate the 'Firmware' or 'Downloads' section for the Archer C64
  3. 3. Check for any firmware versions newer than 1.15.0 that address security vulnerabilities
  4. 4. If a newer firmware is available, download it from the official TP-Link site only
  5. 5. Access the Archer C64 web management interface
  6. 6. Navigate to the System or Administration settings
  7. 7. Locate the firmware upgrade option and upload the downloaded firmware file
  8. 8. Wait for the upgrade process to complete - do not power off the device
Caveat Review firmware release notes for any configuration or feature changes that may affect deployment

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Archer C64 Firmware Scoped from the published advisory
  • Consultation4.0 h
  • Implementation6.0 h
  • Testing3.0 h
  • Review / QA2.0 h
15.0 hours of engineering $2,690
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $4,304.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-8697 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2026-8697 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data