# CVE-2026-36734: Command injection in n/a

> An authenticated attacker can execute arbitrary system commands on EDIMAX BR-6428nS V3 routers via crafted WLAN configuration input.

- **Severity:** High 8.8 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H`)
- **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:** 11 May 2026
- **Updated:** 5 Jul 2026
- **Also known as:** GHSA-c9c6-xfr6-q42w

## What is CVE-2026-36734?

CVE-2026-36734 is a high-severity command injection vulnerability in n/a, published on 11 May 2026. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

EDIMAX BR-6428nS V3 1.15 is vulnerable to Command Injection. An authenticated attacker with access to the network can submit crafted input to the WLAN configuration functionality. Due to insufficient input validation, the attacker is able to execute arbitrary system commands on the device.

Weakness: CWE-77 (Improper Neutralization of Special Elements used in a Command)

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


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

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

## Is CVE-2026-36734 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-36734 is a high-severity command injection vulnerability in n/a, published on 11 May 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-36734 in the wild and no public exploit code.

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

## Sources

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

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