# CVE-2026-94097: Netcore NBR200V2 CGI Diagnostic Endpoint network_tools command injection

> Remote attackers can execute arbitrary commands on Netcore NBR200V2 routers via the network_tools CGI endpoint due to improper input validation.

- **Severity:** Critical 10.0 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:H/VA:H/SC:H/SI:H/SA:H/E:P`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 20 Sep 2026
- **Updated:** 24 Sep 2026
- **Also known as:** GHSA-7jpq-3q84-h4j2

## What is CVE-2026-94097?

CVE-2026-94097 is a critical command injection vulnerability in Netcore NBR200V2, published on 20 Sep 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

A vulnerability was determined in Netcore NBR200V2 1.3.241127.071246. This affects an unknown part of the file /www/cgi-bin/network_tools of the component CGI Diagnostic Endpoint. This manipulation of the argument param/key/val causes command injection. Remote exploitation of the attack is possible. The exploit has been publicly disclosed and may be utilized. The vendor was contacted early about this disclosure but did not respond in any way.

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-94097?


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

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

## Is CVE-2026-94097 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-94097 is a critical command injection vulnerability in Netcore NBR200V2, published on 20 Sep 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-94097 in the wild and no public exploit code.

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

## Sources

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

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