Skip to content
Networks

CVE-2026-19586

9.3
Critical
EPSS 6%Patch availableAug 22, 2026

Pre-auth command injection in Omada gateways' OpenVPN server enabling RCE

common questions

Is CVE-2026-19586 being exploited?

Not confirmed. CVE-2026-19586 does not appear in CISA's Known Exploited Vulnerabilities catalog, which records only exploitation that has been observed and reported publicly. That is evidence of absence of a report, not evidence the flaw is unattacked. EPSS currently estimates a 5.7% probability of exploitation in the next 30 days.

How severe is CVE-2026-19586?

CVE-2026-19586 is rated Critical with a CVSS score of 9.3. Severity describes how bad exploitation would be, not how likely it is: pair it with exploitation evidence before deciding what to patch first.

Is there a patch for CVE-2026-19586?

Yes. A fix has been recorded for CVE-2026-19586. The vendor advisory is the authority on the exact fixed version — apply it from there rather than from a summary.

What does CVE-2026-19586 affect?

CVE-2026-19586 affects TP-Link Omada gateways with OpenVPN Server enabled. Confirm the exact affected versions against the vendor advisory before deciding you are exposed.

What should I do about CVE-2026-19586?

Disable OpenVPN Server, restrict/ACL VPN access, monitor logs, apply vendor patch when released.

Exploitation status reflects CISA's KEV catalog as we last synced it. Check the catalog directly.

executive summary
technical analysis
affected
TP-Link Omada gateways with OpenVPN Server enabled
impact

Unauthenticated attacker can execute arbitrary OS commands via crafted OpenVPN inputs, enabling full device compromise and network pivot.

action required

Immediate action required

affected versions
TP-Link Systems Inc. DR3150 v1
  • affected< 1.0.1 Build 20260722 Rel.16854
TP-Link Systems Inc. DR3220v-4G v1
  • affected< 1.2.0 Build 20260630 Rel.82652
TP-Link Systems Inc. DR3650v-4G v1
  • affected< 1.2.0 Build 20260630 Rel.83347
TP-Link Systems Inc. DR3650v v1
  • affected< 1.2.0 Build 20260630 Rel.83311
TP-Link Systems Inc. ER603WP-4G-Outdoor v1
  • affected< 1.0.2 Build 20260723 Rel.43271
TP-Link Systems Inc. ER605 v2
  • affected< 2.4.4 Build 20260630 Rel.14398
TP-Link Systems Inc. ER605W v2
  • affected< 2.0.4 Build 20260723 Rel.43763
TP-Link Systems Inc. ER701-5G-Outdoor v1
  • affected< 1.0.3 Build 20260723 Rel.40931
TP-Link Systems Inc. ER703WP-4G-Outdoor v1
  • affected< 1.1.7 Build 20260723 Rel.41712
TP-Link Systems Inc. ER706W-4G v2
  • affected< 2.1.11 Build 20260723 Rel.41624
TP-Link Systems Inc. ER706WP-4G v1
  • affected< 1.1.11 Build 20260723 Rel.41624
TP-Link Systems Inc. ER706W v1
  • affected< 1.2.11 Build 20260723 Rel.41567
TP-Link Systems Inc. ER707-M2 v1
  • affected< 1.4.4 Build 20260625 Rel.43063
TP-Link Systems Inc. ER7206 v2
  • affected< 2.3.5 Build 20260625 Rel.43136
TP-Link Systems Inc. ER7212PC v2
  • affected< 2.4.3 Build 20260722 Rel.40250
TP-Link Systems Inc ER7406 v1
  • affected< 1.3.4 Build 20260625 Rel.43136
TP-Link Systems Inc ER7412-M2 v1
  • affected< 1.2.0 Build 20260630 Rel.82947
TP-Link Systems Inc. ER8411 v1
  • affected< 1.4.1 Build 20260708 Rel.64832
TP-Link Systems Inc. v1
  • affected< 1.2.6 Build 20260723 Rel.41321

As published in the CVE Program record. A version outside these ranges is not a statement that it is unaffected — vendors sometimes understate a range, and distribution-backported builds carry upstream numbers that do not reflect what was patched into them.

how to fix
Remediation steps are tailored for users whose stack is affected. Add this technology to your stack to see the fix checklist.
references
get alerted

Track only the vulnerabilities that affect your infrastructure.

start for free