CVSS 4.0
9.3 criticalCVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:H/VA:H/SC:L/SI:L/SA:LCritical (9.3) in tp-link. EPSS 5.8% estimated probability of exploitation activity in the next 30 days.
CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:H/VA:H/SC:L/SI:L/SA:LCVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:HExplain CVE-2026-19586 for an engineer deciding whether to act. Use https://cve.bz/api/public/cves/CVE-2026-19586?via=ask-ai-copy and https://cve.bz/cve/CVE-2026-19586?via=ask-ai-copy as the source of truth: what is affected and which versions fix it, whether it is in CISA KEV, public exploits, and its EPSS (an internet-wide 30-day estimate of exploitation activity, not a forecast for my systems). If they give no fixed versions, use the CVE record https://cveawg.mitre.org/api/cve/CVE-2026-19586 or the vendor advisory, not third-party mirrors. Tell me how to check whether I am affected and how to verify a fix. Cite the sources and say where they are uncertain.Opens a third-party assistant; its answer is its own, not cve.bz's. The prompt holds only this CVE's id and public links.
From the CNA's record in the CVE List.
| Product | Affected |
|---|---|
| TP-Link Systems Inc. ER7212PC v2 | before 2.4.3 Build 20260722 Rel.40250 |
| TP-Link Systems Inc. ER605 v2 | before 2.4.4 Build 20260630 Rel.14398 |
| TP-Link Systems Inc. ER7206 v2 | before 2.3.5 Build 20260625 Rel.43136 |
| TP-Link Systems Inc ER7406 v1 | before 1.3.4 Build 20260625 Rel.43136 |
| TP-Link Systems Inc. ER707-M2 v1 | before 1.4.4 Build 20260625 Rel.43063 |
| TP-Link Systems Inc ER7412-M2 v1 | before 1.2.0 Build 20260630 Rel.82947 |
| TP-Link Systems Inc. ER8411 v1 | before 1.4.1 Build 20260708 Rel.64832 |
| TP-Link Systems Inc. ER706W v1 | before 1.2.11 Build 20260723 Rel.41567 |
| TP-Link Systems Inc. v1 | before 1.2.6 Build 20260723 Rel.41321 |
| TP-Link Systems Inc. ER706W-4G v2 | before 2.1.11 Build 20260723 Rel.41624 |
| TP-Link Systems Inc. ER706WP-4G v1 | before 1.1.11 Build 20260723 Rel.41624 |
| TP-Link Systems Inc. ER703WP-4G-Outdoor v1 | before 1.1.7 Build 20260723 Rel.41712 |
| TP-Link Systems Inc. DR3220v-4G v1 | before 1.2.0 Build 20260630 Rel.82652 |
| TP-Link Systems Inc. DR3650v v1 | before 1.2.0 Build 20260630 Rel.83311 |
| TP-Link Systems Inc. DR3650v-4G v1 | before 1.2.0 Build 20260630 Rel.83347 |
| TP-Link Systems Inc. ER603WP-4G-Outdoor v1 | before 1.0.2 Build 20260723 Rel.43271 |
| TP-Link Systems Inc. DR3150 v1 | before 1.0.1 Build 20260722 Rel.16854 |
| TP-Link Systems Inc. ER701-5G-Outdoor v1 | before 1.0.3 Build 20260723 Rel.40931 |
| TP-Link Systems Inc. ER605W v2 | before 2.0.4 Build 20260723 Rel.43763 |
Repositories on GitHub named after this CVE or listed for it by the PoC-in-GitHub index. For those marked Harbor Check: matches CVE, Flawharbor read the code and found it implements this CVE's exploitation technique: read, not run, and its dependencies only checked for warning signs, so a pointer and no guarantee. The rest are unverified: some hold a working proof of concept, some nothing useful, and some malware made to look like one. Read the code before you run any of it.
The attack patterns MITRE's CAPEC relates to this record's weaknesses, as MITRE names them. Credits.