Menu

Star on GitHub · 3.2k

CVE-2026-17252

A stack-based out-of-bounds write vulnerability exists in the login request handling functionality of the administrative web interface of TP-Link TL-MR6400 v7 routers.

Published Aug 21, 2026CWE-787EPSS 0.27%

Overview

CVE-2026-17252 is a known-severity vulnerability. It was published on August 21, 2026.

Technical description

A

stack-based out-of-bounds write vulnerability exists in the login request

handling functionality of the administrative web interface of TP-Link TL-MR6400 v7 routers. An unauthenticated adjacent attacker can trigger the vulnerability

by sending a specially crafted malformed HTTP request.

Successful

exploitation may cause the web service process to crash, resulting in a

denial-of-service condition and temporary loss of access to the router's web

management interface.

Remediation

Check the references section for vendor advisories, patches, and mitigation guidance. If immediate patching is not possible, review the CVSS vector to understand the attack surface and apply compensating controls such as network segmentation or access restrictions.

Frequently asked questions

What is CVE-2026-17252?

CVE-2026-17252 is a known-severity vulnerability. It was published on August 21, 2026.

How severe is CVE-2026-17252?

CVSS score information is not yet available for this vulnerability. Check back as the CVE record is updated by NVD analysts.

How do I fix or remediate CVE-2026-17252?

Check the references section for vendor advisories, patches, and mitigation guidance. If immediate patching is not possible, review the CVSS vector to understand the attack surface and apply compensating controls such as network segmentation or access restrictions.

How can CyberStrike help with CVE-2026-17252?

CyberStrike is an open-source, AI-augmented pentesting engine. Rather than flag a version number, it tests whether an issue like CVE-2026-17252 is actually reachable in your own applications and APIs, then verifies each finding before reporting it. That tells you if the weakness is a real, exploitable risk in your environment or a false positive you can safely deprioritize.