# CVE-2026-19586: Pre-Authentication OS Command Injection in Omada Gateways on OpenVPN Server in Omada Gateways

> Unauthenticated attackers can execute arbitrary commands on Omada gateways if the OpenVPN Server feature is enabled, leading to full device compromise.

- **Severity:** Critical 9.3 (`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`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 20 Aug 2026
- **Updated:** 28 Aug 2026
- **Also known as:** GHSA-32hp-8pjq-2c8g

## What is CVE-2026-19586?

CVE-2026-19586 is a critical command injection vulnerability in TP-Link Systems Inc DR3150 v1, published on 20 Aug 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

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.

Weakness: CWE-78 (Improper Neutralization of Special Elements used in an OS Command)

## Which versions are affected by CVE-2026-19586?

It affects 18 products.


Products: Tp-Link Dr3150 Firmware, Tp-Link Dr3220v-4g Firmware, Tp-Link Dr3650v-4g Firmware, Tp-Link Dr3650v Firmware, Tp-Link Er603wp-4g-Outdoor Firmware, Tp-Link Er605 Firmware, Tp-Link Er605w Firmware, Tp-Link Er701-5g-Outdoor Firmware, Tp-Link Er703wp-4g-Outdoor Firmware, Tp-Link Er706w-4g Firmware, Tp-Link Er706w Firmware, Tp-Link Er706wp-4g Firmware, Tp-Link Er707-M2 Firmware, Tp-Link Er7206 Firmware, Tp-Link Er7212pc Firmware, Tp-Link Er7406 Firmware, Tp-Link Er7412-M2 Firmware, Tp-Link Er8411 Firmware.

## How do I fix CVE-2026-19586?

No fix has been published for CVE-2026-19586 yet. Limit exposure of the affected software until one is available.

## Is CVE-2026-19586 being exploited?

There is no known exploitation of CVE-2026-19586 in the wild and no public exploit code.

Public exploit code:

- Proof of Concept (PoC) for the TP-Link Omada SSL VPN Unauthenticated RCE (CVE-2026-19586) (github_poc): https://github.com/mattgsys/CVE-2026-19586

## Other vulnerabilities in TP-Link Systems Inc DR3150 v1

- [CVE-2026-19683](https://insights.sbomify.com/CVE-2026-19683/): Unencrypted Credential Transmission in Omada Gateway Dynamic DNS Authentication in Omada Gateways (medium 6.3)
- [CVE-2026-9033](https://insights.sbomify.com/CVE-2026-9033/): Unauthenticated Captive Portal Session Termination and Forced Logout in Omada Gateways (medium 6.0)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-19586 and fix it if it is affected.

What it is: CVE-2026-19586 is a critical command injection vulnerability in TP-Link Systems Inc DR3150 v1, published on 20 Aug 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-19586 in the wild and no public exploit code.

Affected product: TP-Link Systems Inc DR3150 v1. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-19586/ (Markdown: https://insights.sbomify.com/CVE-2026-19586/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-19586
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-19586
- OSV: https://osv.dev/vulnerability/CVE-2026-19586

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-19586/
Summaries are generated and may contain mistakes; the official description above is the record.