# CVE-2026-88275: GV-LPC2011/LPC2211 - Wireless WPA-PSK Command Injection

> An administrator can inject shell commands via WPA-PSK settings to execute arbitrary code as root on GeoVision wireless controllers.

- **Severity:** High 7.2 (`CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** An administrator
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 10 Sep 2026
- **Updated:** 10 Sep 2026
- **Also known as:** GHSA-g92f-j55q-7ccp

## What is CVE-2026-88275?

CVE-2026-88275 is a high-severity command injection vulnerability in GeoVision Inc. GV-LPC2011/LPC2211, published on 10 Sep 2026. An attacker needs administrator access to exploit it, with no action from the victim.

### Official description

GeoVision GV-LPC2211 V1.13 allows an administrator-controlled WPA-PSK containing shell syntax to execute arbitrary commands as root when wireless configuration is applied.

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

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


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

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

## Is CVE-2026-88275 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-88275 is a high-severity command injection vulnerability in GeoVision Inc. GV-LPC2011/LPC2211, published on 10 Sep 2026. An attacker needs administrator access to exploit it, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-88275 in the wild and no public exploit code.

Affected product: GeoVision Inc. GV-LPC2011/LPC2211. 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-88275/ (Markdown: https://insights.sbomify.com/CVE-2026-88275/index.md)
```

## Sources

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

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