Cyber & AI intelligence
Briefs indexed3924
Issues37
Published Mondays07:30 CT
⚡ Active KEV CVE-2026-132622 2026-11-18

GearUP Hyperev OS Command Injection in WLAN Site Survey (CVE-2026-132622)

"CVE-2026-132622 is a critical, remotely exploitable OS command injection flaw in the WLAN Site Survey component of GearUP Hyperev up to version 20261020, and the vendor has not responded to disclosure."

CVE-2026-132622 is a critical, remotely exploitable OS command injection flaw in the WLAN Site Survey component of GearUP Hyperev up to version 20261020, and the vendor has not responded to disclosure.

What Is It

The flaw sits in the get_wlan_sitesurvey function in the file ld/utils.lua, which is part of Hyperev's WLAN Site Survey component. By manipulating the line argument, an attacker can inject operating system commands. The CNA (VulDB) classifies the weakness as CWE-77 (Command Injection) and CWE-78 (OS Command Injection). The attack can be carried out remotely.

Why It Matters

VulDB rates the flaw CVSS 3.1 9.1 (CRITICAL) with vector CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:C/C:H/I:H/A:H. The CVSS 4.0 score is 9.4 (CRITICAL), and the CVSS 2.0 score is 8.3 (HIGH). The attack runs over the network with low complexity and needs no user interaction. Confidentiality, integrity and availability impacts are all rated high, and the scope is changed, so impact can reach past the vulnerable component.

The main limit is that exploitation requires high privileges, which means an attacker must already have privileged access to reach the vulnerable function.

The CISA KEV entry supplied for this CVE is empty. KEV does not confirm active exploitation, and the CVSS 4.0 exploit maturity field is "Not Defined." NVD lists the record's status as "Deferred."

What's Vulnerable

Patch Status

The source data lists no patch or fixed version. According to the disclosure, the vendor was contacted early but did not respond. There is no CISA KEV entry, so no federal required action or due date applies.

Until the vendor publishes a fix, organizations running Hyperev should: - Limit who holds privileged access to the device. - Watch the VulDB entries below for updates.

Sources