Vulnerability Threat research · Edge
Netcore NBR200V2: command injection through traceroute
A router diagnostic accepts more than a destination address. For the team responsible for the device, the immediate questions are who can reach that interface and what the router can reach in return.
- Named firmware
- 1.3.241127.071246
- Access in CVE record
- Low privileges PR:L
- VulDB CNA score
- 9.9 CVSS v3.1
Source: CVE-2026-94095. The CNA also lists CVSS v4.0 at 9.4. Scores describe severity, not observed attack volume.
01 / The flaw
The destination field crosses into command execution
CVE-2026-94095 identifies command injection in the traceroute function of Netcore NBR200V2 firmware 1.3.241127.071246. The affected binary is /usr/bin/network_tools, and the input is named url. The CVE record was published on September 20, 2026 and reports that an exploit is public. CNA record
In the researcher's disclosure, that value arrives through a ubus JSON-RPC request and is incorporated into a shell command without adequate input handling. A value intended to identify the host to trace can instead introduce commands. The researcher reports arbitrary command execution. FirmHarness submission
That changes what diagnostic access means. A feature intended to troubleshoot a connection becomes a way to act on the router's operating system. The consequences for an organization depend on the router's permissions, its network position, and the controls around it.
02 / The access requirement
Remote does not mean unauthenticated
The CVE record's severity vectors specify PR:L, meaning low privileges are required before exploitation. VulDB's separate narrative calls the attack unauthenticated, which conflicts with those metrics. We use the structured CVE record for the access requirement. CNA metrics · VulDB narrative
- 01 / Reachability
Reach the interface
A route to the diagnostic service.
Check WAN, LAN, and VPN paths - 02 / Privileges
Low privileges
The CNA records
Review permitted accountsPR:L. - 03 / Vulnerable input
Command injection
The traceroute input enters a shell command.
Confirm the vendor's fix
Illustration of the disclosed conditions, not a captured attack session. Turning off WAN administration does not remove internal management access.
For an operator, this is a reason to examine management accounts and internal access, not just the public IP address. A compromised workstation or remote-access account may already have a route to equipment that is never directly exposed to the internet.
03 / Remediation status
Fix status and exploitation evidence
As of September 22, we did not identify a vendor fix in the sources reviewed. Netcore's download page still lists the named firmware, and its release notes do not identify a correction for this CVE. The CNA reports that the vendor did not respond to the disclosure. Ask Netcore or the supplier for a supported remediation path rather than treating the presence of a firmware download as evidence of a fix. Vendor downloads · Named build's release notes
The CVE was not listed in the CISA Known Exploited Vulnerabilities feed checked on September 22. Public exploit availability warrants attention, but it is not the same as confirmed exploitation. Prioritize the device using its actual exposure and operational role. CISA KEV
04 / From our decoys · August 15, 2026
A ping field carrying shell commands
Our FortiGate- and Lantronix-emulating decoys each received a POST to an IPv6 ping form on August 15. The submitted pingAddr value contained backtick shell substitution and commands to download and invoke a file. The retained request bodies were identical and came from the same observed source address about 26 minutes apart.
POST /boaform/adminformLogout//boaform/admin/formPing6
Field: pingAddr Backtick shell substitution
Submitted command sequence
cdChange directorywgetRetrieve a filechmodChange permissions- Relative pathInvoke the file
Same body received by
2 request records Matching bodies
The labels describe instructions in the recorded field, not execution results. Command arguments, the download destination, and the filename are omitted.
These are related diagnostic-input injection attempts, not evidence of CVE-2026-94095 exploitation or a vulnerability in the products the decoys emulate. The useful connection is the input: a field intended for a network destination was used to carry shell instructions. Investigate that pattern in management requests alongside unexpected outbound connections from the device.
05 / What to verify
What I would ask the network team to verify
- Keep: inventory record
Find the device and its owner
Record the exact model, firmware, site, and service it supports. Match this disclosure to the installed build. Do not extend the affected-version claim to every Netcore or Netis router.
- Keep: access-test results
Test management reachability from the right places
Remove unneeded WAN administration. Restrict management and diagnostics to approved administration hosts, then verify the effective rules from authorized WAN, user, guest, and VPN locations. Include IPv6 and alternate paths where enabled. Use access checks, not an exploit, on production equipment.
- Keep: account and role review
Review the accounts that can use diagnostics
Remove stale access and replace shared or default credentials. Confirm which roles can invoke the feature. If the device cannot enforce the required restriction, place the access control on a separate trusted management boundary.
- Keep: tested boundary rules
Limit what a compromised router could reach
Enforce sensitive-network restrictions on an independent firewall or other trusted boundary. A VLAN label does not provide isolation when the potentially compromised router controls the routing. Coordinate changes with the service owner, especially for remote or operational sites.
- Keep: remediation or recovery decision
Set an owner and date for remediation
Confirm the fixed firmware's applicability, then install it and verify the resulting build and service operation. If a supported fix cannot be obtained, plan replacement with a tested configuration and rollback path. If compromise is suspected, preserve available logs and configuration evidence before reset or reflash when operationally safe.
06 / What to monitor
Monitor the router's behavior, not just the login page
Small appliances rarely provide the same telemetry as a managed server. Use the records you can obtain from the device, an independent firewall, DNS, and the management network. The useful signal is a change that the owner cannot explain.
Unexpected diagnostic use
Review the source, account, time, and target against approved support work. Retain request metadata where available without collecting credentials or session tokens.
New destinations or services
Investigate unexplained outbound SSH, file transfers, or recurring connections. Compare them with approved management, update, and monitoring traffic.
Unapproved changes
Check DNS settings, routes, accounts, and forwarding rules against a trusted baseline. A change without an owner deserves investigation.
A diagnostic utility may legitimately invoke a shell. A shell-child event alone is not a reliable detection for this flaw. Likewise, a command-injection filter is an additional control, not a replacement for restricted access and remediation.
The useful outcome is a verified access boundary, an accountable remediation plan, and enough visibility to investigate activity that should not be there.
07 / Reference material
Sources and verification
Checked September 22, 2026. The Netcore analysis is based on public disclosure records, not an independent reproduction. The separate first-party example comes from retained August 15 HTTP traffic to our research decoys.
- Official CVE record, VulDB CNA: affected build, component, publication date, exploit status, and severity vectors.
- FirmHarness researcher submission: reported input-to-shell mechanism via ubus JSON-RPC.
- Netcore release notes and firmware index: reviewed for a supported fix.
- CISA KEV feed: no matching entry in catalog version 2026.09.21.
- FIRST CVSS specification: meaning of privileges required.
- Deception Check research fleet: two HTTP request records from the FortiGate- and Lantronix-emulating decoys. Request bodies and parsed field values were compared directly. Archive references and integrity hashes are retained internally.
Technical reference
- Classification
- CNA: CWE-77 and CWE-74
- CVSS v3.1 base vector
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:H/A:H- CVSS v4.0 record vector
CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:H/VI:H/VA:H/SC:H/SI:H/SA:H/E:P- Scope of this review
- The available primary material does not establish a demonstrated root shell or persistence. Those claims are not used here.