# CVE-2026-88289: GV-LPC2011/LPC2211 - Multiple Pre-Authentication Stack Buffer Overflows in VLSVR Request Handlers

> Unauthenticated remote attackers can crash the VLSVR service on GeoVision LPC2011/LPC2211 devices via stack buffer overflows in request handlers.

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

## What is CVE-2026-88289?

CVE-2026-88289 is a high-severity memory corruption vulnerability in GeoVision Inc. GV-LPC2011/LPC2211, published on 10 Sep 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

GeoVision GV-LPC2211 V1.14 (260903) fails to validate attacker-controlled variable-length fields before copying them into fixed-size stack buffers in multiple VLSVR request handlers, allowing an unauthenticated remote attacker to crash the VLSVR service.

Weakness: CWE-121 (Stack-based Buffer Overflow)

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


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

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

## Is CVE-2026-88289 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-88289 is a high-severity memory corruption vulnerability in GeoVision Inc. GV-LPC2011/LPC2211, published on 10 Sep 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-88289 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-88289/ (Markdown: https://insights.sbomify.com/CVE-2026-88289/index.md)
```

## Sources

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

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