On this page (7 sections)

CVE-2026-124585 is an OS command injection flaw in the web administration interface of Chengdu Feiyuxing Technology VW2100 and VEC10GP devices, firmware version 1.0 B-MB3W202-210825-r11775. According to the GitHub Advisory Database entry, it can be attacked remotely, a public exploit exists, and the vendor did not respond when contacted about the disclosure.

If you run one of these devices, or manage them for clients, the practical concern is that no fixed version is listed anywhere in the available research. That makes network exposure control the main defense for now.

What happened

The flaw was published on November 9, 2026 and appears in the GitHub Advisory Database and the NVD record. The NVD text repeats the same description, so it is not separate confirmation. Only one independent source covers the story so far.

The description says the exploit has been made public and could be used, and that the vendor was contacted early but never replied. The records link to a proof-of-concept repository and to VulDB entries. We have not reviewed or reproduced that material, and this article does not include any exploit detail.

Technical details

The weakness sits in the function add_expmac in the file var/html/webserver, part of the Web Administration Interface. Manipulating the mac argument leads to OS command injection. The CVE is tagged with CWE-77 and CWE-78, both command injection classes.

In plain terms, command injection happens when a device takes a value a user typed, here a MAC address field, and passes it to the underlying operating system without properly restricting what it contains. Instead of being treated as plain data, parts of the input can be interpreted as commands. On an embedded network device that can give an attacker control over the device, which is why the impact ratings below are all high.

Severity metrics

The CVSS v4 metrics listed in the GitHub advisory are:

  • Attack vector: network, so it can be attempted remotely
  • Attack complexity: low, and no attack requirements
  • Privileges required: low, meaning some level of login to the interface appears to be needed
  • User interaction: none
  • Impact: high for confidentiality, integrity and availability, on both the vulnerable and subsequent systems
The low privileges requirement is a metric value, not a statement about how authentication works on these devices. The research does not describe the login behavior in detail, so do not assume the interface is safe just because it asks for a password.

Who is affected

The records name two products, VW2100 and VEC10GP, at firmware 1.0 B-MB3W202-210825-r11775. The advisory lists affected and patched versions as unknown, so other firmware builds may or may not be affected. Treat any device in these product lines as potentially exposed until the vendor says otherwise.

Risk is highest where the web administration page is reachable from the internet or from large, loosely controlled internal networks. A device that is only reachable from a dedicated management network is much harder to attack.

How to check your exposure

Start with an inventory. Identify any VW2100 or VEC10GP units, note their firmware string in the admin interface, and compare it to 1.0 B-MB3W202-210825-r11775.

Then check whether the admin interface is reachable from where it should not be. From a machine outside your network, test whether the device's management address answers on its web ports. The commands below only attempt a connection and report success or failure. Replace the placeholder with your device's public address; if a connection succeeds, the admin interface is exposed on that port.

Test whether a device's web ports are reachable (run from a host outside your network)Shell
nc -vz DEVICE_PUBLIC_IP 80
nc -vz DEVICE_PUBLIC_IP 443

Also review the device and any upstream firewall logs for unexpected requests to the admin interface, and for configuration changes, new accounts or unfamiliar outbound connections you did not make.

What to do now

  1. List every VW2100 and VEC10GP device and record its firmware version.
  2. Remove the web administration interface from the public internet. Block it at the upstream firewall or router.
  3. Restrict admin access to a dedicated management network or a small set of trusted IP addresses, or require a VPN.
  4. Change administrator passwords on affected devices and do not reuse them elsewhere.
  5. Contact Chengdu Feiyuxing Technology or your supplier and ask for a fixed firmware or an official statement.
  6. Review logs and device configuration for signs of tampering, and keep a record of the current known-good configuration.
  7. If a device has been exposed and you see suspicious behavior, treat it as compromised: isolate it, rotate credentials that passed through it, and consider replacing it.
Caution. Changing firewall rules or restarting a network device can interrupt connectivity for everything behind it. Schedule the change, and keep an out-of-band way to reach the device before you lock down remote access.
Tip. If the vendor stays silent, plan for replacement. A device with a public exploit and no patch path is a long-term liability, and segmenting it is a stopgap, not a fix.

Detection and monitoring

Because no patch is listed, ongoing monitoring matters. Watch for repeated requests to the admin interface from unfamiliar addresses, unexpected reboots, changed settings, and outbound traffic from the device to hosts you do not recognize.

For public-facing sites and services behind such devices, Webforta Monitor can track uptime, certificate and DNS changes, which can help you notice side effects if a gateway is tampered with. A website firewall helps for web applications, but it does not protect the device's own management interface, so network-level restrictions remain essential. For broader guidance, see website security for small business.

What is still unknown

  • Whether any fixed firmware exists or is planned; the advisory lists patched versions as unknown.
  • Whether other firmware builds or related products are affected.
  • Whether the flaw is being exploited in the wild. A public exploit is reported, but no source confirms active attacks.
  • How authentication on the interface works in practice, beyond the low privileges metric.

We will update this article if the vendor responds or more sources confirm details.

Sources

This article is based on the public sources below. Details can change as vendors and researchers publish more; check the original advisories before acting on version numbers.

  1. CVE-2026-124585 - GitHub Advisory Databasegithub.com
  2. CVE-2026-124585: A vulnerability was found in Chengdu Feiyuxing Technology VW2100 and VEC10GP 1.0 B-MB3W202-210825-r11775.nvd.nist.gov ·
  • CVE-2026-124585
  • Feiyuxing
  • command injection
  • network devices
  • no patch