cve.bz

CVE-2026-19586 tp-link: OS Command Injection

9.3 criticalExploit referenceEPSS 5.8%

Critical (9.3) in tp-link. EPSS 5.8% estimated probability of exploitation activity in the next 30 days.

On this page
A pre-authentication OS command injection vulnerability has been identified in Omada gateways configured to operate as an OpenVPN Server due to insufficient validation of client-supplied data during OpenVPN connection establishment. An unauthenticated remote attacker may provide specially crafted input influencing backend command execution logic before authentication completes. Exploitation requires the OpenVPN Server feature to be enabled, VPN service reachable by the attacker and attacker to be able to initiate an OpenVPN connection attempt.  Successful exploitation may allow arbitrary command execution, potentially leading to full compromise of the affected device.

Severity

CVSS 4.0

9.3 critical
CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:H/VA:H/SC:L/SI:L/SA:L

CVSS 3.1

9.8 critical
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
EPSS
5.8% (unchanged from 5.8% a week ago; 5.7% 30 days ago) estimated probability of exploitation activity in the next 30 days; 93rd percentile. Scored 2026-11-15. A forecast for this CVE across the internet, not for your own systems.
CISA's assessment (SSVC)
Exploitation: none · Automatable: yes · Technical impact: total, assessed 2026-08-20. From CISA's Vulnrichment in the CVE List: whether it is exploited, whether exploiting it can be automated, and how much control it gives.
CWE
CWE-78 Improper Neutralization of Special Elements used in an OS Command (OS Command Injection)
OWASP Top 10
A05:2025 Injection
Published
Modified
NVD analysis
Analyzed
Record from
the NVD, synced

Fix and patched versions

Ask an AI about this CVE

Show the promptExplain 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.

Badge for a README or a site

CVE-2026-19586

An image that stays current: it is drawn from the data each time it is fetched (a host that proxies images, as GitHub does, may show its copy for a while). Markdown:

[![CVE-2026-19586](https://cve.bz/cve/badge/CVE-2026-19586.svg)](https://cve.bz/cve/CVE-2026-19586)

HTML:

<a href="https://cve.bz/cve/CVE-2026-19586"><img src="https://cve.bz/cve/badge/CVE-2026-19586.svg" alt="CVE-2026-19586"></a>

Affected

Versions

From the CNA's record in the CVE List.

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

GitHub PoC

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.

  • mattgsys/CVE-2026-19586 Harbor Check: matches CVE 3 stars, Python, created
    Proof of Concept (PoC) for the TP-Link Omada SSL VPN Unauthenticated RCE (CVE-2026-19586)

Attack patterns (CAPEC)

  • CAPEC-6 Argument Injection Likelihood: High · Severity: High
  • CAPEC-15 Command Delimiters Likelihood: High · Severity: High
  • CAPEC-43 Exploiting Multiple Input Interpretation Layers Likelihood: Medium · Severity: High
  • CAPEC-88 OS Command Injection Likelihood: High · Severity: High
  • CAPEC-108 Command Line Execution through SQL Injection Likelihood: Low · Severity: Very High

The attack patterns MITRE's CAPEC relates to this record's weaknesses, as MITRE names them. Credits.

References

Check your stackJSON