CVE-2026-8619 — Unauthenticated Denial-of-Service Vulnerability in HTTP Service in TP-Link TL-MR100, TL-MR150, TL-MR6400 and Archer MR600
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.
Who exploits it and how urgent it is
A 0–100 score combining confirmed exploitation, ransomware and APT use, public exploits, EPSS and severity.
How the score was calculated
- Technical severity (high)+6
The score orders the patch queue; it does not replace your asset context (internet exposure, criticality, compensating controls).
Triage
Is it exploited, how likely is exploitation, what does it touch, and how severe do the sources call it.
CISA SSVC assessment CISA
Three decision points CISA publishes for the CVEs it assesses (SSVC 2.0.3). A stakeholder decision, not a severity score.
Remediation
Fixes and mitigations documented by the sources — linked to the original advisory.
No fix documented by the sources we poll. That does not mean none exists: check the vendor advisory.
First 24 hours
Ordered from the record’s own fields — exposure first, because you cannot patch what you have not found. A rule-generated starting point.
- Identify exposed assets running the affected vendor/product/version combinations (TP-Link Systems Inc. Archer Mr600 Firmware, TP-Link Systems Inc. Archer MR600 v2, TP-Link Systems Inc. Tl-mr100 Firmware…).
- The attack is network-based and needs no privileges: restrict exposure (ACLs, VPN, WAF) until patched.
- No fix documented in the sources: reduce exposure and monitor the vendor advisory.
- Search available logs for exploit probes matching the vulnerability class (memory corruption), errors and authentication anomalies.
Affected scope
Vendor, product and versions as the sources word them.
| Vendor | Product | Versions | Status | Source |
|---|---|---|---|---|
| TP-Link Systems Inc. | Archer Mr600 Firmware | < 1.10.0 | Vulnerable | NIST National Vulnerability Database |
| TP-Link Systems Inc. | Archer MR600 v2 | < Archer MR600(EU)_V2_1.10.0 Build 260618 | Vulnerable | CVE Program (cve.org) e CISA ADP |
| TP-Link Systems Inc. | Tl-mr100 Firmware | < 1.3.0 | Vulnerable | NIST National Vulnerability Database |
| TP-Link Systems Inc. | TL-MR100 v3.2 | < TL-MR100(EU)_V3.20_1.3.0 Build 260609 Rel.49957n | Vulnerable | CVE Program (cve.org) e CISA ADP |
| TP-Link Systems Inc. | Tl-mr150 Firmware | < 1.3.0 | Vulnerable | NIST National Vulnerability Database |
| TP-Link Systems Inc. | TL-MR150 v.3.2 | < TL-MR150(EU)_V3.20_1.3.0 Build 260720 Rel.59727n | Vulnerable | CVE Program (cve.org) e CISA ADP |
| TP-Link Systems Inc. | Tl-mr6400 Firmware | < 1.5.0 | Vulnerable | NIST National Vulnerability Database |
| TP-Link Systems Inc. | TL-MR6400 v8.0 | < TL-MR6400(EN)_V8_1.5.0 Build 260610 Rel.67978n | Vulnerable | CVE Program (cve.org) e CISA ADP |
Attack characteristics
The CVSS vector, decoded. It describes the attack, not your exposure to it.
Every base score collected
Sources score independently and may disagree; each row says who scored it and under which version.
| Score | Version | Severity | Expl. | Impact | Scored by |
|---|---|---|---|---|---|
| 7.1 | CVSS 4.0 | High | — | — | f23511db-6c3e-4e32-a477-6aa17d310630 via NIST National Vulnerability Database |
| 7.1 | CVSS 4.0 | High | — | — | TPLink via CVE Program (cve.org) e CISA ADP |
| 7.5 | CVSS 3.1 | High | 3.9 | 3.6 | nvd@nist.gov via NIST National Vulnerability Database |
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H (score shown at the top: nvd@nist.gov) Weakness MITRE
Weakness class according to MITRE’s CWE catalog.
Detection
Read off the CVSS vector and the weakness class. Starting points, not tested rules.
- Prioritize edge telemetry for the network-reachable component (proxy, WAF, IDS/IPS).
- Correlate service crashes/restarts with inbound traffic; repeated crashes may indicate attempts.
Timeline
What happened to this CVE, newest first.
- 2026
- Affected products added · tp-link systems inc./tl-mr100 v3.2, tp-link systems inc./tl-mr150 v.3.2, tp-link systems inc./tl-mr6400 v8.0, tp-link sy
- SSVC assessment updated
- Record published
- CVSS changed · 7.5
- Source status changed · → Analyzed
- Record created in this database
- CVE published
Source activity
Repeated readings are counted rather than listed.
- 1× Official description updated · Oct 15, 2026 – Oct 15, 2026
References
5 on the record
Elsewhere on this site
Related CVEs (same products)
- Medium CVE-2026-12339 Authenticated Arbitrary File Write Vulnerability in multiple devices Aug 10, 2026
- High CVE-2026-3841 Command Injection Vulnerability in Telnet CLI on TP-Link TL-MR6400 Mar 12, 2026
- High CVE-2025-14756 Authenticated Command Injection Vulnerability in Archer MR600 Jan 26, 2026
Not in any source we poll
Listed rather than left blank: an empty field and an unmeasured one look identical on screen, and only one is a reason to look elsewhere.
- No FIRST EPSS score.
- No fixed version, patch or mitigation documented.
- No confirmed IOCs, IP addresses, domains, file hashes, or malware artifacts supplied.
- No organization-specific asset inventory, compensating-control status, or patch deployment evidence supplied.
- No exploit packet captures, log samples, or incident case IDs supplied.
Answered from this record
Text assembled only from the fields above — no additional claims.
What should defenders know first?
CVE-2026-8619 is "Unauthenticated Denial-of-Service Vulnerability in HTTP Service in TP-Link TL-MR100, TL-MR150, TL-MR6400 and Archer MR600", rated High. It affects Archer Mr600 Firmware (TP-Link Systems Inc.); versions are in the scope table. It is not in CISA KEV, which does not rule out exploitation. CVSS 7.5 describes technical severity. First verify whether exposed or business-critical assets run the affected versions, apply vendor fixes or mitigations, and preserve logs for review.
Comments
Moderated technical discussion. Read the community guidelines.
No comments yet.
Sign in or create an account to comment and suggest corrections.