# CVE-2026-4537: Cudy TR1200 ipsec.lua action_ipsec_conn command injection

> Remote attackers can execute arbitrary commands on Cudy TR1200 routers via a command injection flaw in the IPsec configuration interface.

- **Severity:** Medium 5.1 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:H/UI:N/VC:L/VI:L/VA:L/SC:N/SI:N/SA:N/E:P`)
- **Exploited in the wild:** Not known
- **Login needed:** An administrator
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 22 Mar 2026
- **Updated:** 29 Apr 2026
- **Also known as:** GHSA-cgfg-qq46-f464

## What is CVE-2026-4537?

CVE-2026-4537 is a medium-severity command injection vulnerability in Cudy TR1200, published on 22 Mar 2026. An attacker needs administrator access to exploit it, with no action from the victim.

### Official description

A vulnerability was determined in Cudy TR1200 R46-2.4.15-20250721-164017. Impacted is the function action_ipsec_conn of the file /usr/bin/lib/lua/luci/controller/ipsec.lua. Executing a manipulation can lead to command injection. The attack may be launched remotely. The exploit has been publicly disclosed and may be utilized. Upgrading the affected component is advised. The vendor explains, that "some other customer has reported this to us before. And we have fixed this."

Weakness: CWE-77 (Improper Neutralization of Special Elements used in a Command), CWE-74 (Improper Neutralization of Special Elements in Output Used by a Downstream Component)

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


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

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

## Is CVE-2026-4537 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-4537 exists.

## Fix prompt for AI coding agents

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

What it is: CVE-2026-4537 is a medium-severity command injection vulnerability in Cudy TR1200, published on 22 Mar 2026. An attacker needs administrator access to exploit it, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-4537 exists.

Affected product: Cudy TR1200. 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-4537/ (Markdown: https://insights.sbomify.com/CVE-2026-4537/index.md)
```

## Sources

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

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