# CVE-2026-129103: Cudy TR3000 before 2.5.42 Command Injection via Scheduled Reboot Time


- **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-472f-rrmv-pjr2

## What is CVE-2026-129103?

CVE-2026-129103 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 command injection vulnerability that allows authenticated administrators to execute commands as root by injecting newlines into reboot_time. Attackers can submit a reboot_time value followed by a newline and crontab line, which /etc/init.d/autoreboot writes to the root crontab for crond to run.

Weakness: CWE-93 (Improper Neutralization of CRLF Sequences)

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


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

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

## Is CVE-2026-129103 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-129103 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-129103 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-129103/ (Markdown: https://insights.sbomify.com/CVE-2026-129103/index.md)
```

## Sources

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

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