# CVE-2025-62501: SSH Hostkey Misconfiguration Vulnerability in Archer Devices

> Attackers can intercept SSH host keys via MITM to steal device credentials, enabling unauthorized access to TP-Link Archer AX53 routers.

- **Severity:** High 7.0 (`CVSS:4.0/AV:A/AC:L/AT:N/PR:L/UI:P/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Local or same network only
- **Victim action needed:** A user has to click or open something
- **Fix available:** No
- **Published:** 3 Feb 2026
- **Updated:** 22 Oct 2026
- **Also known as:** GHSA-32vw-wgfh-pxr5

## What is CVE-2025-62501?

CVE-2025-62501 is a high-severity vulnerability in TP-Link Systems Inc. Archer AX53 v1.0, published on 3 Feb 2026. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link.

### Official description

SSH Hostkey misconfiguration vulnerability in Archer AX53 and Archer BE3600 (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.

Weakness: CWE-322 (Key Exchange without Entity Authentication)

## Which versions are affected by CVE-2025-62501?

It affects 1 product.


Products: Tp-Link Archer Ax53 Firmware.

## How do I fix CVE-2025-62501?

No fix has been published for CVE-2025-62501 yet. Limit exposure of the affected software until one is available.

## Is CVE-2025-62501 being exploited?

There is no known exploitation of CVE-2025-62501 in the wild and no public exploit code.

## Other vulnerabilities in TP-Link Systems Inc. Archer AX53 v1.0

- [CVE-2025-62673](https://insights.sbomify.com/CVE-2025-62673/): Heap-based Buffer Overflow Vulnerability in Archer AX53 and AX12 (high 8.6)
- [CVE-2026-30815](https://insights.sbomify.com/CVE-2026-30815/): OS Command Injection Vulnerability in OpenVPN Module in TP-Link AX53 (high 8.5)
- [CVE-2026-30818](https://insights.sbomify.com/CVE-2026-30818/): OS Command Injection Vulnerability in dnsmasq Module in TP-Link AX53 (high 8.5)
- [CVE-2025-15608](https://insights.sbomify.com/CVE-2025-15608/): Buffer Overflow in Network Probe Handling Function of TP-Link Archer AX53 + Archer AX55 (high 7.7)
- [CVE-2026-30814](https://insights.sbomify.com/CVE-2026-30814/): Buffer Overflow Vulnerability in TP-Link AX53 (high 7.3)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2025-62501 and fix it if it is affected.

What it is: CVE-2025-62501 is a high-severity vulnerability in TP-Link Systems Inc. Archer AX53 v1.0, published on 3 Feb 2026. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2025-62501 in the wild and no public exploit code.

Affected product: TP-Link Systems Inc. Archer AX53 v1.0. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2025-62501/ (Markdown: https://insights.sbomify.com/CVE-2025-62501/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2025-62501
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2025-62501
- OSV: https://osv.dev/vulnerability/CVE-2025-62501

---
From sbomify Insights: https://insights.sbomify.com/CVE-2025-62501/
Summaries are generated and may contain mistakes; the official description above is the record.