# CVE-2026-29797: Red Lion Controls N-Tron 700 Series Download of Code Without Integrity Check

> Unauthenticated attackers can push malicious firmware to Red Lion N-Tron devices via SNMP/TFTP, leading to remote code execution and full device compromise.

- **Severity:** High 8.4 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:L/VI:H/VA:N/SC:L/SI:H/SA:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 9 Oct 2026
- **Updated:** 11 Oct 2026
- **Also known as:** GHSA-p567-rmrg-wwq4

## What is CVE-2026-29797?

CVE-2026-29797 is a high-severity missing authorization vulnerability in Red Lion Controls 700 Series, published on 9 Oct 2026. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

No authentication is required when updating firmware or bootloader, making it easy for malicious files to be pushed to the device. Additionally, anyone with the same software can scan a network for N-Tron devices and push/pull firmware without authenticating by using SNMP/TFTP.

Weakness: CWE-494 (Download of Code Without Integrity Check)

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


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

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

## Is CVE-2026-29797 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-29797 is a high-severity missing authorization vulnerability in Red Lion Controls 700 Series, published on 9 Oct 2026. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-29797 in the wild and no public exploit code.

Affected product: Red Lion Controls 700 Series. 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-29797/ (Markdown: https://insights.sbomify.com/CVE-2026-29797/index.md)
```

## Sources

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

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