On this page (7 sections)
A critical vulnerability, CVE-2026-132622, was published on 2026-11-19 for GearUP Hyperev up to 20261020. According to the NVD record, the WLAN Site Survey component contains an OS command injection that can be reached remotely. The record also says the vendor was contacted early about the disclosure but did not respond in any way.
If you run, manage or host GearUP Hyperev devices or services, treat this as an unpatched issue for now. The public record lists no fixed version, so the practical work is reducing exposure and watching for abnormal behavior. Only one independent publisher covers this story so far, so details may change.
What was disclosed
The NVD entry describes a flaw in the function get_wlan_sitesurvey in the file ld/utils.lua, part of the WLAN Site Survey component. Manipulating the argument named line leads to OS command injection. The record states the attack can be carried out remotely. The published date is 2026-11-19, and the references point to VulDB entries (VulDB CVE page).
The sources do not say what authentication, if any, is needed to reach the function, which device models or builds are involved beyond the version string, or whether a proof of concept is public. Those points are unconfirmed, so do not assume the flaw is either easy or hard to reach.
Why command injection matters
OS command injection happens when software builds a system command from input it received and does not neutralize that input first. An attacker who controls the input can make the underlying system run commands the developer never intended. The typical result is code execution with the privileges of the vulnerable service, which on embedded or appliance-style software is often a very high level.
The weakness classes listed, CWE-77 and CWE-78, are the generic and OS-specific forms of this problem. A function that handles Wi-Fi site survey data is a common place for this bug, because values such as network names or scan parameters get passed to command-line tools. That is general background on the weakness class, not a statement of how this specific flaw works, which the research does not detail.
Who is realistically exposed
- Organizations running GearUP Hyperev at version 20261020 or earlier, where the version is the only affected range the record gives.
- Deployments where the management or site survey interface is reachable from the internet or from untrusted internal segments.
- Hosting and managed service providers who run these devices or services on behalf of customers and may not have them in a regular patch inventory.
If you are unsure whether you use this product, check asset inventories, procurement records and network scans for the product name. Products that arrive bundled or rebranded are often missed.
How to check your exposure
Start with identifying where Hyperev runs and which build it is. The record gives the affected range as up to 20261020, so any build at or below that value should be treated as affected until the vendor says otherwise.
- List every GearUP Hyperev instance you own or manage, with its version or build identifier.
- Compare each build against the affected range (20261020 and earlier).
- Find out which network each instance's management and WLAN Site Survey functions are reachable from, including any port forwarding or public IP exposure.
- Check whether the vendor has published a newer build or advisory since 2026-11-19, and record the date you checked.
Review web server or device logs for requests to the site survey function that contain shell metacharacters or unusual values in a parameter called line. This is a read-only check. Adjust the log path to your environment, as the research does not name one.
grep -i 'sitesurvey' /path/to/access.log | lessLook for requests from unfamiliar addresses, repeated requests, or odd characters in the parameter. A match is not proof of compromise, but it tells you where to look more closely.
What to do now
With no fix listed and a vendor that has not responded, the goal is to limit who can reach the vulnerable function and to be ready to patch quickly.
- Inventory all GearUP Hyperev instances and note their build versions.
- Remove direct internet exposure of the device or service and its management interface; place it behind a VPN or an IP allowlist.
- Restrict access to the WLAN Site Survey function to the few administrators who need it, if the product allows that.
- Segment the device from sensitive systems so a compromise cannot easily reach internal data or credentials.
- Change any credentials, API keys or secrets stored on or reachable from the device if you suspect abuse.
- Put a web application firewall or reverse proxy in front of any web-facing interface, and block requests with shell metacharacters in unexpected parameters. This reduces risk but is not a fix.
- Contact GearUP through every channel you have, ask for an advisory and a fixed build, and record the answer.
- Plan a replacement or isolation path in case no patch ever ships.
Detection and monitoring afterwards
Because the weakness allows command execution, compromise may show up as unexpected behavior on the device or the network around it rather than as an obvious website defect.
- New or unexpected outbound connections from the device, especially to addresses you do not recognize.
- Unexplained processes, scheduled tasks or changed files on the device, where you have shell or file access.
- Configuration changes, new accounts or changed passwords you did not make.
- Spikes in requests to the management interface or the site survey function in access logs.
- Unexpected reboots or performance drops.
If the device serves a public website or sits next to one, outside-in checks help catch changes you did not make. Webforta's monitoring can alert you to certificate, DNS and header changes, and the free malware scanner gives a quick look at a public site. Neither can see inside a device or confirm this specific flaw. If you find signs of compromise, follow the steps in website hacked: what to do.
What is still unknown
- Whether the vendor will publish a fix or an advisory.
- Whether authentication is required to reach the vulnerable function.
- Whether exploit details are public or attacks are happening. The research reports no exploitation and no CISA KEV listing as of 2026-11-19.
- Exactly which products or builds beyond the version string are affected.
Treat the CVSS score of 9.4 as the figure shown in the CVE record; the research does not say which organization assigned it. Check the NVD page again for updates, and revisit your mitigations once the vendor responds.
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.
