Menu

Star on GitHub · 3.2k

CVE-2026-8619

An unauthenticated denial-of-service vulnerability was identified in TP-Link TL-MR100 v3.2, TL-MR150 v3.2, TL-MR6400 v8.0 and Archer MR600 v2, due to improper handling of exceptional request condit…

Published Aug 20, 2026CWE-476EPSS 0.87%

Overview

CVE-2026-8619 is a known-severity vulnerability. It was published on August 20, 2026.

Technical description

An

unauthenticated denial-of-service vulnerability was identified in TP-Link TL-MR100 v3.2, TL-MR150 v3.2, TL-MR6400 v8.0 and Archer MR600 v2, due to improper handling of exceptional request conditions

that may lead to a NULL pointer dereference. 

A remote attacker on an adjacent network can send a specially crated

HTTP request to trigger a crash of the HTTP service process.

Successful

exploitation may cause the HTTP service to crash, making the web management

interface and HTTP-dependent functionality temporarily unavailable.

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

CVE-2026-8619 is a known-severity vulnerability. It was published on August 20, 2026.

How severe is CVE-2026-8619?

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

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

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