Skip to main content
Press slash or control plus K to focus the search. Use the arrow keys to navigate results and press enter to open a threat.
Reconnecting to live updates…

CVE-2025-62501: CWE-322 Key Exchange without Entity Authentication in TP-Link Systems Inc. Archer AX53 v1.0

0
High
VulnerabilityCVE-2025-62501cvecve-2025-62501cwe-322
Published: Tue Feb 03 2026 (02/03/2026, 18:52:54 UTC)
Source: CVE Database V5
Vendor/Project: TP-Link Systems Inc.
Product: Archer AX53 v1.0

Description

SSH Hostkey misconfiguration vulnerability in TP-Link Archer AX53 v1.0 (tmpserver modules) allows attackers to obtain device credentials through a specially crafted man‑in‑the‑middle (MITM) attack. This could enable unauthorized access if captured credentials are reused.This issue affects Archer AX53 v1.0: through 1.3.1 Build 20241120.

AI-Powered Analysis

AILast updated: 02/03/2026, 19:29:48 UTC

Technical Analysis

CVE-2025-62501 is a vulnerability identified in the TP-Link Archer AX53 v1.0 router series, specifically related to the tmpserver modules handling SSH connections. The root cause is a misconfiguration of the SSH host key exchange process, categorized under CWE-322 (Key Exchange without Entity Authentication). This flaw allows an attacker positioned on the same network path to perform a man-in-the-middle (MITM) attack during the SSH handshake. Because the device does not properly authenticate the entity on the other end of the connection, the attacker can intercept and capture the device credentials transmitted over SSH. These credentials, if reused, can grant unauthorized access to the device, potentially leading to further compromise of the network. The vulnerability requires the attacker to have network access (attack vector: adjacent network) and some user interaction but does not require elevated privileges on the device. The CVSS 4.0 score is 7 (high), reflecting the significant impact on confidentiality, integrity, and availability, with a relatively low attack complexity. The issue affects firmware versions through 1.3.1 Build 20241120, and as of the published date, no patches or known exploits in the wild have been reported. This vulnerability highlights the risk of improper cryptographic implementations in network devices, which can undermine secure remote management.

Potential Impact

For European organizations, this vulnerability poses a significant risk to network security, particularly for those relying on TP-Link Archer AX53 routers for critical connectivity. Successful exploitation can lead to credential theft, enabling attackers to gain unauthorized administrative access to routers. This can result in network traffic interception, manipulation, or disruption, impacting confidentiality, integrity, and availability of organizational data and services. Sectors such as telecommunications, finance, healthcare, and government agencies that deploy these routers in sensitive environments are especially vulnerable. The reuse of captured credentials could facilitate lateral movement within corporate networks, escalating the scope of compromise. Additionally, the vulnerability could be leveraged to establish persistent footholds or launch further attacks against connected systems. Given the widespread use of TP-Link devices in small to medium enterprises and home offices across Europe, the threat surface is considerable. The lack of current patches increases exposure duration, emphasizing the need for immediate mitigations.

Mitigation Recommendations

1. Immediately segment networks to isolate TP-Link Archer AX53 devices from critical infrastructure and sensitive data flows, limiting attacker access to the router management interfaces. 2. Disable SSH access to the router from untrusted networks or restrict it to specific, trusted IP addresses using access control lists. 3. Enforce the use of strong, unique credentials for router management to reduce the risk of credential reuse exploitation. 4. Monitor network traffic for signs of MITM attacks, such as unexpected SSH host key changes or anomalous connection patterns. 5. Employ network-level protections like DHCP snooping, dynamic ARP inspection, and port security to reduce the risk of MITM attacks on local networks. 6. Regularly audit router configurations to ensure SSH host keys are properly generated and managed. 7. Stay informed on vendor advisories and apply firmware updates or patches promptly once released. 8. Consider deploying alternative secure remote management solutions that incorporate robust entity authentication mechanisms. 9. Educate users and administrators about the risks of MITM attacks and the importance of verifying SSH host keys before establishing connections.

Need more detailed analysis?Upgrade to Pro Console

Technical Details

Data Version
5.2
Assigner Short Name
TPLink
Date Reserved
2025-10-21T12:06:08.417Z
Cvss Version
4.0
State
PUBLISHED

Threat ID: 6982493ef9fa50a62fdabaf9

Added to database: 2/3/2026, 7:15:10 PM

Last enriched: 2/3/2026, 7:29:48 PM

Last updated: 2/6/2026, 1:23:20 AM

Views: 9

Community Reviews

0 reviews

Crowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.

Sort by
Loading community insights…

Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.

Actions

PRO

Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.

Please log in to the Console to use AI analysis features.

Need more coverage?

Upgrade to Pro Console in Console -> Billing for AI refresh and higher limits.

For incident response and remediation, OffSeq services can help resolve threats faster.

Latest Threats