CVE
Shenzhen Cudy TR3000 remote code execution as root via OpenVPN config import
Affects Cudy TR3000 1.0 firmware before 2.5.42 when the router connects to an attacker-controlled VPN endpoint using a malicious OpenVPN configuration. Fixed in 2.5.42.
Written by anthropic/claude-haiku-5.5 from the sources below. Verify against them.
CVSS:4.0/AV:N/AC:L/AT:N/PR:H/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N
- Exploited
- No known exploitation
- Fix
- Fixed in 2.5.42
- Who is exposed
- Specific setups only
Do first: Check whether your setup matches what the bug needs. Cudy TR3000 firmware before 2.5.42 (TR3000 1.0, versions >= 0 and < 2.5.42). Router connects to an attacker-controlled VPN endpoint using the malicious OpenVPN configuration.
- Last modified
- Whether it needs action now or is a reference record, by fixed rules, with why. Last checked is when cve.now last re-read it.What do these mean? →
- Reference
- Last checked
- FIRST's estimate of the chance attackers exploit it in the next 30 days, updated daily.What do these mean? →
- 0.87% · 59th percentile
- A 0-100 score for how much a CVE matters across the industry: exploitation, exposure, how widely the software is used, severity and whether a fix exists.What do these mean? →
- 18/100 · provisional
- How many real-world setups can hit the bug, from the vendor's advisory and CISA data. It does not know your setup.What do these mean? →
- Specific setups only
- Whether working attack code is public (Exploit-DB, Metasploit, Nuclei or GitHub). Public code makes attacks easier.What do these mean? →
- None on Exploit-DB, Metasploit or GitHub
- Exploitation: none
- Automatable: no
- Technical impact: total
Summary
The Cudy TR3000 from Shenzhen Cudy Technology Co., Ltd. contains a remote code execution flaw in its OpenVPN configuration import. An attacker with administrator login over the network can import a malicious client configuration that uses tls-verify or ipchange directives, which an incomplete denylist fails to filter, to run commands as root when the router connects to an attacker-controlled VPN endpoint.
Original description
Cudy TR3000 before 2.5.42 contains a remote code execution vulnerability that allows authenticated administrators to run root commands by importing a malicious OpenVPN client configuration. Attackers can include tls-verify or ipchange directives, which the incomplete denylist does not filter, to execute commands as root when the router connects to an attacker-controlled VPN endpoint.
Who should check
Teams and owners running Cudy TR3000 1.0 routers with firmware before 2.5.42, especially where administrators can import OpenVPN client configurations.
“Affecting TR3000 1.0 >= 0, < 2.5.42”
cve.now Index
- Exploitation0/40No signal
- Exposure8/25Specific setups only, reachable over the network
- Reach?/20Unknown. No tracked technology or package matched
- Severity9.6/10CVSS 8.6, total technical impact per CISA
- No patch0/5No signal
What would change the score
- Would score about 68 if added to CISA KEV
- Would score about 63 if CISA's SSVC rates exploitation active
- Would score about 25 if CISA's SSVC rates it automatable
What to do
Check whether your setup matches what the bug needs.
Cudy TR3000 firmware before 2.5.42 (TR3000 1.0, versions >= 0 and < 2.5.42). Router connects to an attacker-controlled VPN endpoint using the malicious OpenVPN configuration.Upgrade to a fixed version: 2.5.42.
Check your systems with an agent
Paste this into a coding or ops agent. It checks your systems read-only and reports a table per asset.
Check whether my systems are affected by CVE-2026-129099 (Cudy TR3000 before 2.5.42 Root RCE via OpenVPN Configuration Import), using the cve.now data below.
Rules: work read-only. Do not run exploit code, proof-of-concept scripts or scanners that send attack payloads, and do not change any configuration, package, image or deployment. Report findings only.
What cve.now has for CVE-2026-129099 (entry last updated 2026-11-13):
Affected:
- Shenzhen Cudy Technology Co., Ltd. TR3000 1.0: fixed in 2.5.42
Fixed versions: 2.5.42.
Conditions (all must be true for the bug to be hit):
- Cudy TR3000 firmware before 2.5.42 (TR3000 1.0, versions >= 0 and < 2.5.42). (source: https://www.vulncheck.com/advisories/cudy-tr3000-before-2.5.42-root-rce-via-openvpn-configuration-import)
- Router connects to an attacker-controlled VPN endpoint using the malicious OpenVPN configuration. (source: https://www.vulncheck.com/advisories/cudy-tr3000-before-2.5.42-root-rce-via-openvpn-configuration-import)
Setup: unknown whether the bug needs a non-default feature or setting. Check the advisory.
Attacker needs: network access, high-privilege login, no user action.
CISA KEV: CVE-2026-129099 is not listed as of cve.now's last read.
This KEV status is for CVE-2026-129099 only. If you also check another CVE, look up its own KEV status; never assume it from this one.
How to check:
- Installed software: check what is actually running, not what a repo declares. Read the version from each host, container image and Kubernetes node (the binary's version output, the OS package database, image layers), and check whether the conditions above hold there. Distribution packages may carry a backported fix under an older version number; confirm against the distribution's own advisory.
Verify against the linked advisories before concluding, and cite the date you read each one:
- https://d1jvyy13vm72kv.cloudfront.net/device/upgrade/m_upgrade_TR3000_256MB_Flash-R103-2.5.42-20261103-160202-sysupgrade_82672.zip
- https://www.cudy.com/en-us/pages/download-center/tr3000-1-0
- https://www.vulncheck.com/advisories/cudy-tr3000-before-2.5.42-root-rce-via-openvpn-configuration-import
Do not conclude an asset is unaffected unless you checked it and the evidence covers both its version and the conditions above. If you could not check something, mark it unknown and say what is missing.
Report a table with one row per asset and these columns: Asset | Version or build | Status (affected, fixed, not applicable, unknown) | Compensating controls | Exposure (internet-facing, internal, none) | Evidence | Next action.
Entry: https://cve.now/CVE-2026-129099
For follow-up questions, use the cve.now MCP server at https://mcp.cve.now/mcp (no authentication), for example execute with name cve.get and arguments {"id": "CVE-2026-129099"}.Timeline
- CVE published
- First seen by cve.now
- CISA SSVC assessment
Exploitation: none · Automatable: no · Technical impact: total
- Record last updated
Affected versions
- Shenzhen Cudy Technology Co., Ltd. TR3000 1.0
fixed in 2.5.42
Evidence 5
Vendor advisory · 1
Establishes: Affected and fixed versions.
- Link
CVE record · 2
Establishes: The identifier and description.
- Record
- Record
Corrections
None so far.
Something wrong on this page? Report an error. Every fix is listed here.
Questions about CVE-2026-129099
Is CVE-2026-129099 being exploited?
It is not in CISA's Known Exploited Vulnerabilities catalog, and CISA's SSVC assessment does not mark exploitation as active. That does not mean it has not been attacked: vendors and researchers can report attacks before CISA lists them. No public exploit code is tracked.Source: cve.now feed data
What does this mean?
Authenticated administrators can run commands as root on the router by importing a malicious OpenVPN client configuration. The result is remote code execution with root privileges.Source: vulncheck.com
Which versions are affected by CVE-2026-129099?
TR3000 1.0: before 2.5.42.Source: cve.now feed data
Am I affected, and how do I check?
Firmware for the TR3000 1.0 before 2.5.42 is affected, in the setup where the router connects to an attacker-controlled VPN endpoint using a malicious OpenVPN configuration. To check, compare the firmware version shown in the router's admin interface with 2.5.42.Source: vulncheck.com
How do I fix CVE-2026-129099?
Upgrade the TR3000 1.0 firmware to 2.5.42.Source: vulncheck.com