# CVE-2026-129100: Cudy TR3000 before 2.5.42 Root RCE via OpenVPN Key Upload Injection


- **Severity:** High 8.6 (`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 in the wild:** Not known
- **Fix available:** No
- **Published:** 13 Nov 2026
- **Updated:** 17 Nov 2026
- **Also known as:** GHSA-5r2m-3p47-vjwj

## What is CVE-2026-129100?

CVE-2026-129100 is a high-severity vulnerability in Shenzhen Cudy Technology Co., Ltd. TR3000 1.0, published on 13 Nov 2026. 

### Official 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.

Weakness: CWE-116 (Improper Encoding or Escaping of Output)

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


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

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

## Is CVE-2026-129100 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-129100 is a high-severity vulnerability in Shenzhen Cudy Technology Co., Ltd. TR3000 1.0, published on 13 Nov 2026. 
Exploitation: There is no known exploitation of CVE-2026-129100 in the wild and no public exploit code.

Affected product: Shenzhen Cudy Technology Co., Ltd. TR3000 1.0. 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-129100/ (Markdown: https://insights.sbomify.com/CVE-2026-129100/index.md)
```

## Sources

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

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