Menu

Star on GitHub · 3.2k

CVE-2026-76651

A buffer overflow vulnerability exists in the embedded HTTP service in TL-WR841N v14 when processing multipart/form-data requests.

Published Aug 28, 2026CWE-120EPSS 0.44%

Overview

CVE-2026-76651 is a known-severity vulnerability. It was published on August 28, 2026.

Technical description

A buffer

overflow vulnerability exists in the embedded HTTP service in TL-WR841N v14 when processing

multipart/form-data requests. Insufficient validation of an attacker-controlled

boundary parameter may allow a remote unauthenticated attacker to submit a

crafted request that corrupts memory by overwriting data beyond the bounds of

an internal buffer.

Successful

exploitation may result in modification or corruption of process memory,

potentially leading to undefined application behavior. Arbitrary code

execution, information disclosure, and denial-of-service conditions have not

been demonstrated.

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-76651?

CVE-2026-76651 is a known-severity vulnerability. It was published on August 28, 2026.

How severe is CVE-2026-76651?

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-76651?

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-76651?

CyberStrike is an open-source, AI-augmented pentesting engine. Rather than flag a version number, it tests whether an issue like CVE-2026-76651 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.