# CVE-2026-132622: GearUP Hyperev WLAN Site Survey utils.lua get_wlan_sitesurvey os command injection


- **Severity:** Critical 9.4 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:H/UI:N/VC:H/VI:H/VA:H/SC:H/SI:H/SA:H/E:X`)
- **Exploited in the wild:** Not known
- **Fix available:** No
- **Published:** 19 Nov 2026
- **Updated:** 19 Nov 2026
- **Also known as:** GHSA-mghg-3mm2-qpm7

## What is CVE-2026-132622?

CVE-2026-132622 is a critical vulnerability in GearUP Hyperev, published on 19 Nov 2026. 

### Official description

A vulnerability was found in GearUP Hyperev up to 20261020. This impacts the function get_wlan_sitesurvey of the file ld/utils.lua of the component WLAN Site Survey. Performing a manipulation of the argument line results in os command injection. The attack is possible to be carried out remotely. The vendor was contacted early about this disclosure but did not respond in any way.

Weakness: CWE-78 (Improper Neutralization of Special Elements used in an OS Command), CWE-77 (Improper Neutralization of Special Elements used in a Command)

## Which versions are affected by CVE-2026-132622?

It affects 1 product.


Products: Gearup Hyperev.

CPE match criteria (CPE 2.3):

- `cpe:2.3:a:gearup:hyperev:*:*:*:*:*:*:*:*` from 20261020 up to 20261020

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

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

## Is CVE-2026-132622 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-132622 is a critical vulnerability in GearUP Hyperev, published on 19 Nov 2026. 
Exploitation: There is no known exploitation of CVE-2026-132622 in the wild and no public exploit code.

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

## Sources

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

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