CVE Tools
Track your stack

CVE-2026-8619

Unauthenticated Denial-of-Service Vulnerability in HTTP Service in TP-Link TL-MR100, TL-MR150, TL-MR6400 and Archer MR600

No known exploitation. EPSS puts it in the 59th percentile. Fixed versions are out.

CVSS 3.17.5HighEPSS percentile59th0.9% chance in 30 daysCISA KEVNot listedNo confirmed exploitation
No public exploit knownFix5 products5 fixed builds listed below
Check it yourself

No ready-made check. Neither Nuclei nor OpenVAS has one for this CVE yet.

Request a scan

Published Updated Sources: CVE.org, NVD

NVD CVE.org

What to do

Find your product and version, then upgrade to the build on the right.

  • TP-Link Systems Inc. TL-MR100 v3.2Affected: < TL-MR100(EU)_V3.20_1.3.0 Build 260609 Rel.49957nUpgrade to: TL-MR100(EU)_V3.20_1.3.0 Build 260609 Rel.49957nStated by: CVE record
  • TP-Link Systems Inc. TL-MR150 v.3.2Affected: < TL-MR150(EU)_V3.20_1.3.0 Build 260720 Rel.59727nUpgrade to: TL-MR150(EU)_V3.20_1.3.0 Build 260720 Rel.59727nStated by: CVE record
  • TP-Link Systems Inc. TL-MR6400 v8.0Affected: < TL-MR6400(EN)_V8_1.5.0 Build 260610 Rel.67978nUpgrade to: TL-MR6400(EN)_V8_1.5.0 Build 260610 Rel.67978nStated by: CVE record
  • TP-Link Systems Inc Archer MR600 v2Affected: < Archer MR600(EU)_V2_1.10.0 Build 260618Upgrade to: Archer MR600(EU)_V2_1.10.0 Build 260618Stated by: CVE record
  • Tp-link Tl-mr100 FirmwareAffected: < 1.3.0Upgrade to: 1.3.0Stated by: NVD

Versions as the sources state them. 3 more products have version data. Full version matrix after sign-in

Is your organisation exposed?Request an assessment to establish which checks fit your systems.

What it is

From the CVE record

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.

In plain language

No plain-language summary for this CVE yet.

Exploitation

Where each signal puts this CVE on the scale from published to confirmed exploited.

EPSS59th
CISA KEV

Not in the catalog. CISA has not confirmed exploitation.

Public exploits

No public exploit or proof of concept found in the sources we track.

EPSS

0.9% chance of exploitation activity in the next 30 days, which ranks it in the 59th percentile of scored CVEs.

Exploit Prediction Scoring System, FIRST.org. A probability, not a confirmation.

Lifecycle

10 events over 69 days, from the signal feeds we watch.

  1. Patch availablerecord updated
  2. Patch availablerecord updated
  3. Record updated
  4. Record updatedrecord updated
  5. Publishedweakness classified, att&ck mapped

Affected products

Technical detail

CVSS 3.1 vector

Open in the CVSS calculator

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H

Scored 7.5 by NVD.

How it is reached

  • Attack Vector NetworkExploitable remotely over the network without any special conditions
  • Attack Complexity LowNo special conditions — the attack can be reliably reproduced
  • Privileges Required NoneNo authentication required — anyone can exploit this
  • User Interaction NoneNo user interaction needed — fully automated exploitation

Scope

  • Scope UnchangedImpact is limited to the vulnerable component itself

Impact if exploited

  • Confidentiality NoneNo confidentiality impact
  • Integrity NoneNo integrity impact
  • Availability HighTotal denial of service — the component is completely unavailable

Weaknesses

ATT&CK techniques

Mapped from the weaknesses above (CWE to ATT&CK), not observed in attacks.

Sources

References in the record

And 2 more references. See all after sign-in

Watch the software you run.

My Stack ranks new CVEs for your products by real-world exploitation, so the next serious one reaches you without reading every advisory.

We'll flag the next CVE, public exploit or patch for Tl-mr100 Firmware, not every advisory.